Nick Reinking wrote:
On Tue, Aug 12, 2003 at 05:25:26AM -0700, Jimmy Wales wrote:
This requests goes out _especially_ to the 'hands dirty' developers who are intricately familiar with where our hardware bottlenecks are most likely to be. But anyone with solid, non-speculative ideas is welcome to comment!
If I remember it right it should be: pliny => datebase and all wikis but en and de ...? larousse => webserver (php) for en and de
If I'm wrong, adapt the following or correct me writing in thes list ;)
I think Nick is right, getting a fast 'php' (Webserver) frontend for all the languages still running on pliny. And giving the database enought memory, and a fast RAID (striping is usually the version with fast read access, if I remember, feel free to correct me) will help to get a database-server only doing mysql and this hopefully at all his speed and memory.
We can in the future easily take a look at the load of the hosts and see what is slowing us down, the database server or the frontend hosts. And we can move languages from one frontend to the other to optimize the load (not all big wiki's on one host etc. ).