On Tuesday 18 April 2006 10:41, Ira Abramov wrote:
> Quoting Shlomi Fish, from the post of Mon, 27 Mar:
> > > Sympa is the only new addition on the server, right ?
> >
> > I think so, yes.
> >
> > > Can you move the lists to beak ? It takes ~20% of memory.
> >
> > The lists reside at the iglu.org.il and linux.org.il domains which are
> > hosted at Eskimo. Moving them to beak would imply moving the domains
> > along with them, as well as the contents of the Sympa database. Assuming
> > this is indeed the problem, I believe it would be much less headache to
> > just buy more RAM for Eskimo, assuming it is indeed needed.
>
> Good luck finding that specific antique flavor of RAM. you may discover
> it will cost you an arm and a leg.
Well, I can always try... Question is whether it will cost more than a brand
new server.
> if I may suggest, eskimo has run its
> course. the CPU and RAM have been stretched to the limits of what this
> hardware can do at a sane cost,
I'm not sure we've reached the limits yet. Eskimo seems to be doing a pretty
fine job at doing what it's doing - it just needs more RAM. A P3 is a fast
processor, and I don't see a need to dump it just yet.
> while over the last 5 years (has it
> really been that long?) we've been loading it with fatter kernels and
> apps, and now dumping the paper-thin qmail for a much fatter postfix,
> and apparently Sympa likes to run as a resident daemon (why on earth?!)
> and take up quite a few unswappable pages of precious RAM.
It is possible that Sympa runs as a daemon because it is written in Perl and
thus its develoeprs wished to save the costy startup time. I'm not entirely
familiar with the Sympa architecture so I cannot comment.
We haven't dumped qmail for postfix yet - it's just something I'd like to do.
>
> moving back to Qmail makes no sense anymore, I say consolidate the mail
> on one server, free up the old one to do what it can still do best, and
> that's high-volume file serving.
Hmmm... making beak our sole web server does seem like an interesting idea. Of
course, beak has the problem of having routinely ran out of disk space
recently. Is it better now?
> move interactive web content off of it,
> have as few interpreters as possible run on it (that means anything
> requiring mod_php, mod_perl, mod_python, perl- and python-based daemons)
> and just let it serve files.
There doesn't seem to be a problem with Eskimo serving interactive or
interpreted web content. It seem to do this very well. Moving the interactive
web content to beak would be very time consuming.
> At our day and age (and bandwidth
> demands) it no longer makes sense to load it with any other tasks, and
> it makes absolutely no sense at all to go out to find the weird RAM this
> machine requires, it will cost an arm and a leg.
Let's first try to find some RAM, OK? If we can't, we'll contemplate what to
do next.
Regards,
Shlomi Fish
---------------------------------------------------------------------
Shlomi Fish [EMAIL PROTECTED]
Homepage: http://www.shlomifish.org/
95% of the programmers consider 95% of the code they did not write, in the
bottom 5%.
