[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Re: If it ain't broke, don't fix it ?
- Subject: Re: [cobalt-users] Re: If it ain't broke, don't fix it ?
- From: "Kevin D" <kdlists@xxxxxxxxxxxxxxx>
- Date: Tue Oct 30 12:45:34 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
> Did you really know what you were looking at ? I am not sure since you
> didn't notice the problem was with analog at over 1/2 the memory usage
> alone.
I'm sorry, you're right, I didn't even notice that line there. I scanned
through what I saw only very quickly - its been a long day, ok??
You might consider rotating some of your web log files so that analog
doesn't have to do as much work. You could also explore alternatives to
analog (webalizer, for one).
Also, note that if you add up all the memory from those mysql processes, you
get 352mb - more than what analog is consuming. You should consider looking
into that.
> The server traffic is less than 200 kb/s and the Raq4r has 512mb ram. Is
> that too much traffic for it to be a problem ? I don't think so, at least
> it shouldn't be. I'm sure many ISPs are using their Raq's with more than
> that for traffic.
200kb/s of constant traffic... do the math... that accounts to over 500GB
per month - which is a lot! How did you arrive at that figure? I assume it
is a snapshot of a given moment of traffic? Besides, traffic in general
isn't really as relevant as what kind of traffic. It looks like your traffic
is largely database driven www, and databases love memory and cpu cycles.
Kevin