I think that the problem here is that we've asked for more info and he hasn't
supplied it. He's given us generics and as a result has gotten generic
answers.
1) What are the average hits per second that you are projecting this box to
handle?
2) What is the peak hits per second that you are project this box to handle?
3) We know you have a gig of ram, but give us info on the rest of the platform?
4) What's your OS like? Solaris, AIX, HP-UX, Linux, FreeBSD, etc. & which
version and/or flavor
5) What other processes are you running?
6) Do you have a Database? Which one? A gig of ram is nothing to Oracle
6a) Will be running queries constantly or will you be caching a lot?
7) What other modules are you running? PhP? SpeedyCGI? Axkit? Cocoon?
In short what is the server DOING at any given moment. Until folks have a feel
for this no one is going to be able to offer you any insight beyond what you
already have.
Perrin Harkins wrote:
> On Thu, 11 Jan 2001, Rob Bloodgood wrote:
> > Second of all, with the literally thousands of pages of docs necessary to
> > understand in order to be really mod_perl proficient
>
> Most of the documentation is really reference-oriented. All the important
> concepts in mod_perl performance tuning fit in a few pages of the guide.
>
> > I mean, 1GB is a lot of ram.
>
> It's all relative. If you have significant traffic on your site, 1GB RAM
> might not be nearly enough.
>
> > And finally, I was hoping to prod somebody into posting snippets of
> > CODE
> > and
> > httpd.conf
> >
> > that describe SPECIFIC steps/checks/modules/configs designed to put a
> > reasonable cap on resources so that we can serve millions of hits w/o
> > needing a restart.
>
> I think you're making this much harder than it needs to be. It's this
> simple:
>
> MaxClients 30
>
> PerlFixupHandler Apache::SizeLimit
> <Perl>
> use Apache::SizeLimit;
> # sizes are in KB
> $Apache::SizeLimit::MAX_PROCESS_SIZE = 30000;
> $Apache::SizeLimit::CHECK_EVERY_N_REQUESTS = 5;
> </Perl>
>
> If you're paranoid, you can throw BSD::Resource in the mix to catch
> things like infinite loops in your code.
>
> None of this will make your code faster or your server bigger. It will
> just prevent it from going into swap. Having too much traffic can still
> hose your site in lots of other ways that have nothing to do with swap and
> everything to do with the design of your application and the hardware you
> run it on, but there's nothing mod_perl-specific about those issues.
>
> - Perrin
--
Jimi Thompson
Web Master
Link.com
"It's the same thing we do every night, Pinky."
