<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.3" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Benchmark MySQL Proxy and HSCALE</title>
	<link>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/</link>
	<description></description>
	<pubDate>Thu, 28 Aug 2008 23:05:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
		<item>
		<title>By: Robert Hodges: Myosotis Connector: a Fast SQL Proxy for MySQL and PostgreSQL &#124; Maildir.net Mailling list archive</title>
		<link>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-4107</link>
		<dc:creator>Robert Hodges: Myosotis Connector: a Fast SQL Proxy for MySQL and PostgreSQL &#124; Maildir.net Mailling list archive</dc:creator>
		<pubDate>Mon, 14 Jul 2008 17:48:09 +0000</pubDate>
		<guid>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-4107</guid>
		<description>[...] As other people have discovered, proxying is very CPU-intensive. It also involves a lot of concurrency, since a proxy may have to manage hundreds or even thousands of connections. Java is already fast in single threads&#8211;after a few runs through method invocations, the JVM has compiled the bytecodes down to native machine code. In addition, Java uses multiple CPUs relatively efficiently. Myosotis uses a thread per connection. Java automatically schedules these on all CPUs and optimizes of memory access in multi-core environment. [...]</description>
		<content:encoded><![CDATA[<p>[&#8230;] As other people have discovered, proxying is very CPU-intensive. It also involves a lot of concurrency, since a proxy may have to manage hundreds or even thousands of connections. Java is already fast in single threads&#8211;after a few runs through method invocations, the JVM has compiled the bytecodes down to native machine code. In addition, Java uses multiple CPUs relatively efficiently. Myosotis uses a thread per connection. Java automatically schedules these on all CPUs and optimizes of memory access in multi-core environment. [&#8230;]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pero</title>
		<link>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-1274</link>
		<dc:creator>pero</dc:creator>
		<pubDate>Mon, 05 May 2008 19:28:39 +0000</pubDate>
		<guid>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-1274</guid>
		<description>Jan,

I re-ran the tests with the current svn version. There are some great improvements to be seen! Take a look at the results here: 

http://pero.blogs.aprilmayjune.org/2008/05/05/update-benchmark-hscale-with-mysql-proxy-070-svn-against-061/

Cheers,

Peter</description>
		<content:encoded><![CDATA[<p>Jan,</p>
<p>I re-ran the tests with the current svn version. There are some great improvements to be seen! Take a look at the results here: </p>
<p><a href="http://pero.blogs.aprilmayjune.org/2008/05/05/update-benchmark-hscale-with-mysql-proxy-070-svn-against-061/" rel="nofollow" >http://pero.blogs.aprilmayjune.org/2008/05/05/update-benchmark-hscale-with-mysql-proxy-070-svn-against-061/</a></p>
<p>Cheers,</p>
<p>Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jan Kneschke</title>
		<link>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-1259</link>
		<dc:creator>Jan Kneschke</dc:creator>
		<pubDate>Mon, 05 May 2008 18:09:29 +0000</pubDate>
		<guid>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-1259</guid>
		<description>You may want to give the SVN version of MySQL Proxy a try. It reduces the caches the compiled lua script and should reduce the overhead of hscale.</description>
		<content:encoded><![CDATA[<p>You may want to give the SVN version of MySQL Proxy a try. It reduces the caches the compiled lua script and should reduce the overhead of hscale.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pero</title>
		<link>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-1237</link>
		<dc:creator>pero</dc:creator>
		<pubDate>Mon, 05 May 2008 16:34:00 +0000</pubDate>
		<guid>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-1237</guid>
		<description>Brian,

mysqlslap was really a great help here. And it worked like a charm! 
As minor improvements: it would be great to get the result for *each* run (to correlate it to vmstat or sar data) and to be able to use multiple statements. 

Greetings,

Peter</description>
		<content:encoded><![CDATA[<p>Brian,</p>
<p>mysqlslap was really a great help here. And it worked like a charm!<br />
As minor improvements: it would be great to get the result for *each* run (to correlate it to vmstat or sar data) and to be able to use multiple statements. </p>
<p>Greetings,</p>
<p>Peter</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Aker</title>
		<link>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-1232</link>
		<dc:creator>Brian Aker</dc:creator>
		<pubDate>Mon, 05 May 2008 16:20:45 +0000</pubDate>
		<guid>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-1232</guid>
		<description>Hi!

Any feedback on Mysqlslap? (positive or negative)

Cheers,
   -Brian</description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>Any feedback on Mysqlslap? (positive or negative)</p>
<p>Cheers,<br />
   -Brian</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kay Roepke</title>
		<link>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-1224</link>
		<dc:creator>Kay Roepke</dc:creator>
		<pubDate>Mon, 05 May 2008 15:54:51 +0000</pubDate>
		<guid>http://pero.blogs.aprilmayjune.org/2008/05/05/benchmark-mysql-proxy-and-hscale/#comment-1224</guid>
		<description>Hi!

Regarding the final thought #2:
Yes, the proxy currently is single-threaded. We are aware of this limitation and it will change in some way in a future release to make proper use of current multi-core/SMP systems.

cheers,
-k</description>
		<content:encoded><![CDATA[<p>Hi!</p>
<p>Regarding the final thought #2:<br />
Yes, the proxy currently is single-threaded. We are aware of this limitation and it will change in some way in a future release to make proper use of current multi-core/SMP systems.</p>
<p>cheers,<br />
-k</p>
]]></content:encoded>
	</item>
</channel>
</rss>
