my first question was about that : it seems that fcgid will _never_ use this concurrent PHP instances. If there is 2 concurrent access, fcgid will spawn an other "group" of PHP to handle that, it will not use the first group of php instance which have idled children. So in this groups of PHP, there is only one php child really used.
If it is just to keep the opcode cache after PHP die (by default all the 500 queries), well, just 1 fork in necessary. Olivier Filip Hajny a écrit : > On 28.2.2009, at 17:05, Olivier B. wrote: > > >> Yes I was thinking that but what is the interest to share memory >> between >> processes which never run simultaneously ? >> >> > > They do. If you let PHP spawn them, they all start right away, and > keep running until you kill them. They are not killed when idle etc. > > F > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Mod-fcgid-users mailing list > Mod-fcgid-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/mod-fcgid-users > ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Mod-fcgid-users mailing list Mod-fcgid-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mod-fcgid-users
