Gerald Richter <[EMAIL PROTECTED]> wrote: > I think what you are doing is correct. I guess the problem is that Perl is > storing it's compiled code and data in the same memory pages, so when the > data gets modified, the code isn't also shared anymore. Embperl 2.0 may > behave better, because it compiled all the code as whole chunck, so it's > less likely that code and data gets mixed up in the same memory page.
That sounds great! > Maybe you gain a little memory by limitied the requests per childs (e.g. to > 100). Since you already have compiled the perl code in the parent, a child > startup should not cost to much. I already set MaxRequestsPerChild to 500, which seems fine at the moment. This isn't a huge deal, I am just thinking about going forward, I'd like the system to be scalable for very large numbers of concurrent users. > Embperl object sets up a search path. You can do the same for your > preloading with the path parameter. Damn, I thought I was missing something here. Thanks. > Apache/mod_perl 2.0 use Perl's ithreads, there Perl will take care to > separate data and code and Perl will make sure to share the code among all > threads. I expected it to be a great inprovement in memory uitlization Again, sounds like the new versions will be very nice. However I have to wait, since I am working like hell on my own stuff at the moment (and on my own time, not getting paid), so not a lot of spare time I'm afraid for debugging Embperl 2.x. Sorry about that, I hope that I'll have more time to play around if/when I actually get a job and/or my own project gets investors... I'm creating a pretty large codebase with Nilspace, using Embperl. Already written a web-based email system similar to Yahoo! or hotmail, but with better folder management and spam control. Also, a web-based agenda (organizer) with contacts manager, links, files, etc... the final component is an e-commerce section that lets websites charge micropayments for sections of their sites, transparently (i.e. without having to change the website files - I wrote a mod_perl access module which you just plug in and then add directives to httpd.conf to specify pay sections, prices etc). All good stuff, all using Embperl. I'll let you know when it's all up and running... All the best -Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
