RE: Server performance update

The increased CPU demand comes from the "ServerSaver" doing its
every-30-second sweep out of expired events (and spit out the
event pool file, if persistence is on).  Glad to hear that it
only consumes 20% of CPU on an unloaded box.  :)

Perhaps the "sweeper" interval should be configurable from the
command line?

Regarding the memory usage, the question I have is, are 25MB
worth of events being spit at it from the Blogchatter and
Presence1 apps per day?  (I believe both of those applications
set their expiry times to a day, so it's entirely possible that
steady-state is about 25MB of unexpired events per day.)

I'll be curious to see what the server does in the next few days.
If it goes up, down, or stabilizes.

I've been running my own Python server for the last four days,
and all events expired over the weekend, so it's running at a
lean 4 Meg.  Not too shabby.

   Adam



-----Original Message-----
From: Joyce Park [mailto:[email protected]]
Sent: Monday, June 02, 2003 11:59 AM
To: [email protected]
Subject: Server performance update

Hi guys, this is an update on the Python server's performance since
implementing the ghetto event-cleaning stuff.  The memory continues
to grow, but much more slowly.  Before, it would get up past 50MB
within a couple of days, and past 100MB in 4 days -- more if we ran
with poolfile.  Now it's about a quarter of that -- 25MB in 4 days.

Balancing that, there's a lot more demand on CPU -- up to 20% or so. 
However, there's nothing else on this web server that needs a lot of
cycles so it's all good.  JP


-------------------------------------------------------
This SF.net email is sponsored by: eBay
Get office equipment for less on eBay!
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5