>Where's the latency being seen? Between the user and the application or
>from the application to the storage?
Thanks guys for the input.
It was between the www servers and the MySQL + JPGs server. We asked
the hoster to add a filer, and performance is much better now, with
the filter being shared between two Apache servers
If demande keeps rising, I guess we'll have to investigate MySQL
clusters, so that the DB doesn't become the bottleneck again.
> If you want to directly connect several servers to the same storage
> you'll need a storage controller which allows multiple devices
> to access the storage and you'll need to install a cluster filesystem.
> That's a load of complexity that you could probably do without.
Yes, that's what I suspected :-/ So I guess the standard solution to
scaling databases is to add some kind of load balancer, and 2 or more
DB servers behind it.
Cydrome Leader - 27 Aug 2008 21:45 GMT
>>Where's the latency being seen? Between the user and the application or
>>from the application to the storage?
[quoted text clipped - 16 lines]
> scaling databases is to add some kind of load balancer, and 2 or more
> DB servers behind it.
It's really to tune things first, then as a last resort, start adding more
hardware. More hardware and more layers is always harder to manage.
As junior as mysql is, there's lots of stuff that can be tweaked. The
apps using it should be examined as well if you are running into
performance problems.
Gilles Ganault - 28 Aug 2008 07:40 GMT
>It's really to tune things first, then as a last resort, start adding more
>hardware. More hardware and more layers is always harder to manage.
I'll make sure MySQL + queries are configured as best as possible.
Thanks.