4 ms·

Another huge load of BS. What is your goal here? > epoll/kqueue Here is the implementation from 2.1, back maybe around 10 years ago: https://github.com/varni

by reza_n 9y ago

Another huge load of BS. What is your goal here? > epoll/kqueue Here is the implementation from 2.1, back maybe around 10 years ago: https://github.com/varnishcache/varnish-cache/blob/2.1/bin/varnishd/cache_waiter_epoll.c https://github.com/varnishcache/varnish-cache/blob/2.1/bin/v... https://github.com/varnishcache/varnish-cache/blob/2.1/bin/varnishd/cache_waiter_kqueue.c https://github.com/varnishcache/varnish-cache/blob/2.1/bin/v... > nginx thread model https://www.nginx.com/blog/thread-pools-boost-performance-9x/ https://www.nginx.com/blog/thread-pools-boost-performance-9x... > With sendfile(2) and splice(2) you are only wiring up the activity to be done in your event loop Why you are storing your cache on disk into individual files when its "2018 and RAM is commonly measured in many hundred GB" is beyond me. But its not even worth discussing because you will just introduce more BS, FUD, and techno babble.

kev009 9y ago
I apologize for being curt here but you haven't demonstrated enough background in computer architecture for me to continue the discussion in a worthwhile way. If you don't understand how nginx workers and varnish workers differ, we operate with different levels of understanding. "babble" is what knowledge sounds like when you've demonstrated to the world in this thread you have no idea how virtual memory works. Feel free to mail me if you think there is something left to debate or want book recommendations on memory management.
- reza_n 9y ago
  I would prefer to keep this public just because its sometimes a good idea to have a record of things like this. I feel this wont be the last time this rears its ugly head. > you've demonstrated to the world in this thread you have no idea how virtual memory works Funny, I kind of consider myself an expert in virtual memory and I previously made no mention of virtual memory in any of my comments. I do consider virtual memory an extremely important part in getting high levels of performance from a cache. Did you confuse sendfile() and copying data from block devices into userspace with virtual memory? Why am I not surprised at this reply.
  - kev009 9y ago
    Nothing to do with sendfile, you claim that TLB management is "a hardware problem" which is completely wrong, whatever you think you know about virtual memory has no foundation and anyone with a basic understanding of computer architecture can tell you that.

by reza_n 9y ago

kev009 9y ago

I apologize for being curt here but you haven't demonstrated enough background in computer architecture for me to continue the discussion in a worthwhile way. If you don't understand how nginx workers and varnish workers differ, we operate with different levels of understanding. "babble" is what knowledge sounds like when you've demonstrated to the world in this thread you have no idea how virtual memory works. Feel free to mail me if you think there is something left to debate or want book recommendations on memory management.

reza_n 9y ago
I would prefer to keep this public just because its sometimes a good idea to have a record of things like this. I feel this wont be the last time this rears its ugly head. > you've demonstrated to the world in this thread you have no idea how virtual memory works Funny, I kind of consider myself an expert in virtual memory and I previously made no mention of virtual memory in any of my comments. I do consider virtual memory an extremely important part in getting high levels of performance from a cache. Did you confuse sendfile() and copying data from block devices into userspace with virtual memory? Why am I not surprised at this reply.
- kev009 9y ago
  Nothing to do with sendfile, you claim that TLB management is "a hardware problem" which is completely wrong, whatever you think you know about virtual memory has no foundation and anyone with a basic understanding of computer architecture can tell you that.