|
Jean-Christophe BOGGIO wrote:
> For now, my idea is to separate read-only queries from write queries :
how about sending all the writes to one realserver, the (rw) realserver and
have the other realservers (ro)? The mysql client will have to be rewritten.
>
> * read queries could be dispatched by the Director to one of the mySQL
> servers (I'm looking for the info for Oracle at this time but the problem is
> the same and I'll have a mySQL project of this kind in a week or two).
> * update/insert/delete queries could be done as many times as there are SQL
> servers. This is at the application level. Don't know if stored procedures
> can access other SQL servers. The application will be heavy to maintain,
> will forbid some mySQL functionnalities but it has a slight chance to work.
> Maybe the system will be slower than having a single mySQL server. I guess
> it depends on the ratio #reads / #writes : the highest the ratio, the best
> speed improvement.
this will only work for read mostly.
> Anyone tested this ?
Jake is working on it.
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
