From: Micah Y. <yo...@ho...> - 2001-08-30 00:07:08
|
When my httpd goes 2 or 3 days without a restart, it appears to be hogging about 300 megs of RAM. My server has 4 Slash sites, none of which are getting a lot of traffic. What gives? Is this a memory leak somewhere or does Slash really take that much memory, with compiled templates & such? I was hoping to get at least 10-15 sites into my 512MB RAM... What are your experiences? Guess I might have to upgrade to a gig or two sooner than I was hoping. -- Like to travel? http://TravTalk.org Micah Yoder Internet Development http://yoderdev.com |
From: Patrick G. <cap...@sl...> - 2001-08-30 03:12:52
|
Micah Yoder wrote: > > When my httpd goes 2 or 3 days without a restart, it appears to be hogging > about 300 megs of RAM. My server has 4 Slash sites, none of which are > getting a lot of traffic. What gives? > > Is this a memory leak somewhere or does Slash really take that much memory, > with compiled templates & such? > decrease the number of httpd processes you have running - if the sites you're running aren't that busy, then you won't be needing as many. Since Slash does so much caching, it does tend to use a good deal of memory. > I was hoping to get at least 10-15 sites into my 512MB RAM... What are your > experiences? Guess I might have to upgrade to a gig or two sooner than I was > hoping. > > -- > Like to travel? http://TravTalk.org > Micah Yoder Internet Development http://yoderdev.com > > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-general |
From: Micah Y. <yo...@ho...> - 2001-08-30 04:05:46
|
> decrease the number of httpd processes you have running - if the sites > you're running aren't that busy, then you won't be needing as many. > Since Slash does so much caching, it does tend to use a good deal of > memory. OK. there are 11 processes now. So compiled Perl modules and cached templates are NOT shared between httpd processes? Will Apache 2 fix this problem with its hybrid thread/process model? Will mod_perl and Slash be able to take advantage of this? Thanks -- Like to travel? http://TravTalk.org Micah Yoder Internet Development http://yoderdev.com |
From: Dave H. <da...@ho...> - 2001-08-30 08:12:30
|
Micah Yoder <yo...@ho...> writes: > > decrease the number of httpd processes you have running - if the sites > > you're running aren't that busy, then you won't be needing as many. > > Since Slash does so much caching, it does tend to use a good deal of > > memory. > > OK. there are 11 processes now. So compiled Perl modules and cached > templates are NOT shared between httpd processes? Sit down and have a good read of the mod_perl guide: http://perl.apache.org/guide/ What you need is to put a "lite" apache on the front and trim the number of Apache processes right back. Also, you _can_ share a truckload of code. The techniques for doing this are again in the guide. > > Will Apache 2 fix this problem with its hybrid thread/process model? Will > mod_perl and Slash be able to take advantage of this? To an extent. -- Dave Hodgkinson, http://www.hodgkinson.org Editor-in-chief, The Highway Star http://www.deep-purple.com Interim CTO, web server farms, technical strategy ---------------------------------------- |
From: Alessio B. <al...@al...> - 2001-08-30 14:54:23
|
Dave Hodgkinson wrote: > Sit down and have a good read of the mod_perl guide: > http://perl.apache.org/guide/ > > What you need is to put a "lite" apache on the front and trim the > number of Apache processes right back. I strongly agree with both suggestions. -- Alessio F. Bragadini al...@al... APL Financial Services http://village.albourne.com Nicosia, Cyprus phone: +357-2-755750 "It is more complicated than you think" -- The Eighth Networking Truth from RFC 1925 |
From: Wakko <una...@ho...> - 2001-08-31 17:06:03
|
Or maybe a more immediate solution is to have redundancy checking in slash. If more than one slash-site is installed, there could be an optional flag to have it only cache one copy of the templates, and share the cache between the sites. However, this would only work if the sites all used the same templates. Though, the big problem would be when more than one site accessed a particular template at the same time. Any sort of file-access queueing would effectively reduce the performance of ALL the installed slash-sites ---Wakko. ----- Original Message ----- From: "Micah Yoder" <yo...@ho...> To: <sla...@li...> Sent: Wednesday, August 29, 2001 6:06 PM Subject: Re: [Slashcode-general] Memory usage > > decrease the number of httpd processes you have running - if the sites > > you're running aren't that busy, then you won't be needing as many. > > Since Slash does so much caching, it does tend to use a good deal of > > memory. > > OK. there are 11 processes now. So compiled Perl modules and cached > templates are NOT shared between httpd processes? > > Will Apache 2 fix this problem with its hybrid thread/process model? Will > mod_perl and Slash be able to take advantage of this? > > Thanks > > -- > Like to travel? http://TravTalk.org > Micah Yoder Internet Development http://yoderdev.com > > > _______________________________________________ > Slashcode-general mailing list > Sla...@li... > http://lists.sourceforge.net/lists/listinfo/slashcode-general > |
From: Dave H. <da...@ho...> - 2001-08-31 20:51:41
|
"Wakko" <una...@ho...> writes: > Or maybe a more immediate solution is to have redundancy checking in slash. > > If more than one slash-site is installed, there could be an optional flag to > have it only cache one copy of the templates, and share the cache between > the sites. If the perl code isn't being shared properly, doing anything with the templates is pointless IMHO. -- Dave Hodgkinson, http://www.hodgkinson.org Editor-in-chief, The Highway Star http://www.deep-purple.com Interim CTO, web server farms, technical strategy ---------------------------------------- |