Re: [Catalyst] server memory usage

2011-04-29 Thread Tomas Doran
On 13 Apr 2011, at 08:25, Jorge Gonzalez wrote: It's plausible that multiple fire-ups of the same program would wind up with identical pages, if no memory allocation ever depends on timing or anything other than static configuration. Could be, but lots of perl modules defer their load

Re: [Catalyst] server memory usage

2011-04-29 Thread Tomas Doran
On 12 Apr 2011, at 13:51, Jorge Gonzalez wrote: Rather, it needs to load all the stuff and _then_ fork, so that the stuff is identical and shared. You are right in this case: the pages would be shared just after the fork, but would probably start to get copied individually for each

Re: [Catalyst] server memory usage

2011-04-12 Thread John M. Dlugosz
On 4/11/2011 8:54 AM, Jorge Gonzalez jorge.gonzalez-at-daikon.es |Catalyst/Allow to home| wrote: You can be assured that it's being done that way. Certainly all modern operating systems do Copy-On-Write on memory pages, which means that several processes with a common set of code will share

Re: [Catalyst] server memory usage

2011-04-12 Thread Tomas Doran
On 11 Apr 2011, at 14:07, John M. Dlugosz wrote: Looking at the server's processes, I see three of script/ myapp_fastcgi.pl, which I suppose co-inside with the Apache configuration option where I said to start 3 fastcgi processes to handle this app. WebMin tells me size, which can't be

Re: [Catalyst] server memory usage

2011-04-12 Thread Jorge Gonzalez
El 12/04/11 12:58, John M. Dlugosz escribió: On 4/11/2011 8:54 AM, Jorge Gonzalez jorge.gonzalez-at-daikon.es |Catalyst/Allow to home| wrote: You can be assured that it's being done that way. Certainly all modern operating systems do Copy-On-Write on memory pages, which means that several

Re: [Catalyst] server memory usage

2011-04-12 Thread John M. Dlugosz
You are right in this case: the pages would be shared just after the fork, but would probably start to get copied individually for each process again as soon as the process starts doing something useful. For perl, which works as some kind of JIT compiler, the script executable code is just

[Catalyst] server memory usage

2011-04-11 Thread John M. Dlugosz
Looking at the server's processes, I see three of script/myapp_fastcgi.pl, which I suppose co-inside with the Apache configuration option where I said to start 3 fastcgi processes to handle this app. WebMin tells me size, which can't be the actual load of server RAM needed since it doesn't

Re: [Catalyst] server memory usage

2011-04-11 Thread Jorge Gonzalez
You can be assured that it's being done that way. Certainly all modern operating systems do Copy-On-Write on memory pages, which means that several processes with a common set of code will share much of it. This is not being done by Apache/fastcgi/Catalyst, but by the very operating system