Version 2 by Peter Romianowski
on Mai 05, 2008 21:52.

<< Changes from 1 to 2
compared with
Current by Peter Romianowski
on Mai 05, 2008 21:54.

 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 0 changes. View first change.

 h1. Performance
  
 HSCALE is designed to as little overhead to your database application as possible. But nothing comes for free ;-)
  
 h2. MySQL Proxy
  
 First of all there is the overhead of using MySQL Proxy. This adds at least another network hop to your client server communication. Benchmark show that in a typical scenario (MySQL Proxy on different host than MySQL server) an overhead of 0.02 milliseconds per query (status: 2008-05-05).
  
 h2. HSCALE
  
 If you add HSCALE to the scenario above it will add up to 0.3 ms to each query compared to the MySQL server.
  
 h2. Benchmarks
  
 * [http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/]
 * [http://pero.blogs.aprilmayjune.org/2008/05/05/update-benchmark-hscale-with-mysql-proxy-070-svn-against-061/]