[OSM-dev] your new sysadmins

[spaetz]

> What is the limiting factor for the T at H server currently? Is it CPU time
> or memory bandwidth or disk I/O bandwidth?

Certainly disk IO, although much of that could probably be alleviated with more RAM. Much of that came from unneccessary mySQL commands of which we have eliminated much. However, the disk which contains all tiles is also quite busy with current upload/download levels. There is still potential once we start spreading tiles over disks.

> This is for dev I take it? Like I say moving it to db2 or something
> might make more sense, and that has 4Gb of RAM at present.

db2 Hardware certainly seems good enough, but for the disk space. Can we take /dev/hdd from dev to db2? I think it's a  PATA disk. That would spare us the copying of 70GB of small files over the network. It's just used for the tiles partition on dev, so removing that one wouldn't hurt dev otherwise.

> Well moving to T at H to db2, which is dual core with 4Gb of RAM, would
> mean we could leave all those ancillary things on dev?

Sure
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
URL: <http://lists.openstreetmap.org/pipermail/dev/attachments/20070808/469dad25/attachment.pgp>