@TrenTorch is now sponsored by @wensitylabs ! ❤️ A huge thank you to Wensity Labs for sponsoring TrenTorch and supporting what we’re building. Go check them out: ui.wensity.com This support will help us improve the platform, build more interactive learning experiences, and keep working toward our vision of making advanced technical learning free and accessible to everyone.

Everyone says learn inference, learn CUDA,learn ML But almost nobody tells you exactly what to learn, how to learn it, or how to know whether you’ve actually learned it. Introducing Trentorch.com a free, open-source platform to learn and practice Machine Learning, CUDA, and inference through hands-on coding. Instead of just watching lectures or reading theory, you’ll: • Learn the theory behind each concept • Follow step-by-step implementation examples • Solve coding challenges based on what you learned • Implement algorithms from scratch, from foundational ML to Inference and CUDA kernel • Practice problems in a Codeforces-style environment • Get new Problem of the Day challenges with ratings The goal isn't just to teach you how to write the code. It’s to help you understand what your code is actually doing underneath. We’re building Trentorch because advanced education shouldn’t be locked behind expensive subscriptions. Money shouldn’t be the barrier to learning ML, inference, or CUDA. A free alternative to platforms that charge students heavily every month. signup and start solving problems now Trentorch.com

I took my C vector database from handling ~1K concurrent requests to 75K by replacing pthreads with epoll. The interesting part wasn't adding more threads. I changed the concurrency model. The old server relied heavily on pthreads, where a thread could sit waiting for one user's I/O to finish. With epoll, the server can monitor thousands of connections at once. While one connection is waiting on I/O, it immediately moves on to another connection instead of leaving a thread blocked. It's the same Linux event-driven I/O mechanism used by NGINX. I benchmarked this on actual VM with 75,000 requests: 204.7 requests/sec average 0.4578s average latency 0.886s p99 latency github github.com/aadityansha06/vec… Special mention @arnavmehta007 for providing VM