<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>tyingq</author><text>This message should probably be repeated at the bottom of the article:&lt;p&gt;&lt;i&gt;&amp;quot;The page cache works pretty well and allows NGINX to demonstrate great performance in almost all common use cases...So if you have a reasonable amount of RAM and your working data set isn’t very big, then NGINX already works in the most optimal way without using thread pools&amp;quot;&lt;/i&gt;&lt;p&gt;So using thread pools in NGINX isn&amp;#x27;t a general recommendation.  The article suggests &amp;quot;a heavily loaded NGINX‑based streaming media server&amp;quot; as the type of situation where it makes sense.</text><parent_chain></parent_chain></comment><story><title>Thread Pools in Nginx Boost Performance 9x (2015)</title><url>https://www.nginx.com/blog/thread-pools-boost-performance-9x/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>Neil44</author><text>As long as you&amp;#x27;re not using Apache in pre-fork mode then the rest boils down to a few percent in terms of http server overhead. Unless you&amp;#x27;re trying to serve tons of little static object with either no resource or big scale then there are better places to spend your time optimizing.</text><parent_chain></parent_chain></comment><story><title>Thread Pools in Nginx Boost Performance 9x (2015)</title><url>https://www.nginx.com/blog/thread-pools-boost-performance-9x/</url></story>