4 ms·
Seems like a rare edge case. Also a bad design IMHO Expanding your network IO handling code to use multiple cores sounds like fun, but it's the wrong way to do
by axod 16y ago
Seems like a rare edge case. Also a bad design IMHO
Expanding your network IO handling code to use multiple cores sounds like fun, but it's the wrong way to do things.
Network handling code is not CPU heavy. Have a single process handling the IO, and for CPU heavy tasks hand off to other threads, handled with callbacks.
I also wish we'd stop benchmarking these sorts of things in NNk requests/second. As if most use cases will get anywhere near that in production.
- swannodette 16y agoSeems like a generalization. People are interested in evented web programming for applications/services that are less traditional in design - where memcached doesn't buy you anything and NNk requests/second do matter. If you're putting your evented application on an 8-core box, you most certainly want to leverage a good number of those cores.
- axod 16y ago>> "If you're putting your evented application on an 8-core box, you most certainly want to leverage a good number of those cores." Unless you're CPU bound, there is absolutely no point.