看完福音戰士新劇場版《破》後,感想太多,先速記如下,日後再作整理。
有劇情,慎入
- 出場後的第一個感覺是:超多內容,有新的有舊的,然後都壓縮在那接近兩小時的片段裏,結果是有點消化不良之餘,還考慮再多看一次,

I was going to say that while preforking accept() -based servers don't in practice have a thundering herdproblem, they do have two other issues, namely there's no way to tellwhen you need to grow the number of processes you're using and no way totell if a process has frozen. (The more complicated preforking scheme has neither problem.)
However, some thought showed me that it's possible to get around theseproblems while retaining the advantages of the pure accept(
For my own curiosity, here is a rundown of what version of Python is invarious current OS distributions, along with whether or not a version ofPython 3 is available as an optional package.
(The version of Python is my best guess at what you get if you runplain ' python ' at a command line.)
| OS | Python version | Optional Python 3? |
| Solaris 10 update 8 | 2.4.4 (2.6 available in Blastwave) | No |
| Red Hat Enterprise 5 (and CentOS 5) | 2 |
看完福音戰士新劇場版《破》後,感想太多,先速記如下,日後再作整理。
有劇情,慎入
For a long time, one of my acquired articles of faith has been thatyou needed to worry about and avoid the thundering herd accept() problem. (This is the problem where ifyou have a bunch of processes all waiting in accept() and a singleconnection comes in, many kernels will wake all of the processes up onlyto have most of them immediately go back to sleep.)
One of the things that Unicorn (via Ryan Tomayko and others )has taught me about preforking servers is that the