3 ms·
> Nginx then introduced a eventloop, which was way better. >A EventLoop mechanism always means that your stuff should be non-blocking and that is hard. hmm ;)
by jackmott 10y ago
> Nginx then introduced a eventloop, which was way better.
>A EventLoop mechanism always means that your stuff should be non-blocking and that is hard.
hmm ;)
So you are saying you need to think about the system your code is running in?
Even an Event Loop server, if CPU utilization is sufficiently highly, paralellizing a function can be counter productive due to overhead and cache thrashing.
- merb 10y ago> if CPU utilization is sufficiently highly that won't be the case in a EventLoop system, it could be the case if you just have too less hardware. But than even your "non paralized" code will fail.