On Thu, 2005-10-06 at 19:57 +0200, Christian Rose wrote:
> > > The only thing needed for the translation status pages to be hosted at
> > > the real, live gnome.org servers is for someone to figure out what kind
> > > of CPU/memory/disk resources it needs, and is prepared to help set it
> > > up, or at least give sufficient instructions for having it set up.
> > >
> > > So what's the required configuration?
> >
> > root gandalf:/srv/l10n # du -hs .
> > 6.9G .
> >
> > and the process takes near 4 hours with an AMD Sempron(tm) 2800+ and
> > 768MB of RAM
> >
> > With more RAM and faster CPU the process should be also faster. The main
> > problem here is the hard disk I/O that's why we had to move it outside
> > widget the first time, the server load was really high.
>
> widget has since then been replaced by window. window.gnome.org is a
> dual Xeon 2.8 GHz server with 2 GB memory and RAID1 SCSI disks.
>
> This should be doable, right?
Something that takes 4 hours of CPU time on window (a day?) probably
isn't a huge deal ... window isn't terribly CPU-bound currently... and
the process could be niced down.
But if it's doing significant disk work - so ejecting stuff out of
cache, then it's going to impact all bugzilla users, all anoncvs users,
all people accessing www.gnome.org etc. window isn't really a good place
to run intensive jobs, because so much is going on there.
In any case, I wouldn't expect things to run faster on window than
on Carlos's machine ... window is a bigger/faster machine, but it's
no monster, and it's a heavily loaded bigger/faster machine.
Disk space is rather tight on window too, though 7 gigs (added to
/etc/rsyncd/backup.exclude appropriately) shouldn't be a big problem
if we keep track.
Things to do:
- Try running it on window, see if it really takes 4 hours, or 2 hours.
(30-45 minutes might be an OK time for an intensive task to churn.)
- Get someone to look at optimizing it. You can do an incredible amount
of work in 4 hours these days ... if this task is taking 4 hours,
it's being done inefficiently. (Not volunteering)
- If it really is that intensive, it's not optimizable, we need it on a
gnome.org server, than container is probably the most appropriate
home:
window: 2 gig ram, 72gig (raid 1) disk, load avg ~1
container: 6 gig ram, 500gig (raid 5) disk, load avg ~0.2
Regards,
Owen
Attachment:
signature.asc
Description: This is a digitally signed message part