>
> Can we also do this with sites built using EmbperlObject in 1.3.x? I would
be very interested in preloading as much as possible so that it can live in
shared memory.
>
Yes, you can do this, but 1.3.x will not always preload everything.
> Do you know offhand what causes memory pages to be cop
Hi,
sorry for the later answer, but this week is a really busy one for me...
>
> We just recently upgraded to 1.3.4 and are suddenly getting random
> segfaults and bus errors.
>
> Server: Stronghold/2.4.2 Apache/1.3.6 C2NetEU/2412 (Unix) mod_perl/1.25
> perl5 (5.0 patchlevel 5 subversion 3)
>
>
> There is one thing which could be done with Apache 1.3 that goes in the same
> direction, also it doesn't save as much memory as using threads. You could
> preload and precompile the pages for Embperl 2.0 in the parent process. As
> long as no writing to these memory locations takes place, the m
