<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How network can impact MySQL Operations ?</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2008/09/01/how-network-can-impact-mysql-operations/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2008/09/01/how-network-can-impact-mysql-operations/</link>
	<description>Everything about MySQL Performance</description>
	<lastBuildDate>Sat, 21 Nov 2009 05:23:57 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2008/09/01/how-network-can-impact-mysql-operations/comment-page-1/#comment-351272</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Tue, 02 Sep 2008 18:28:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=482#comment-351272</guid>
		<description>Pat,

Good notice though in this case I mainly was speaking about switched LAN which normally is quite good with latencies.  Though bunch of routers between servers can affect both latency and throughput dramatically but distance is your worse enemy in this case.

I remember the customer which had performance issues and we asked him how fast is connection between 2 nodes and he told it is 1Gbit direct connection.... though he did not mention the servers actually 100 Miles from each other :)</description>
		<content:encoded><![CDATA[<p>Pat,</p>
<p>Good notice though in this case I mainly was speaking about switched LAN which normally is quite good with latencies.  Though bunch of routers between servers can affect both latency and throughput dramatically but distance is your worse enemy in this case.</p>
<p>I remember the customer which had performance issues and we asked him how fast is connection between 2 nodes and he told it is 1Gbit direct connection&#8230;. though he did not mention the servers actually 100 Miles from each other <img src='http://www.mysqlperformanceblog.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pat</title>
		<link>http://www.mysqlperformanceblog.com/2008/09/01/how-network-can-impact-mysql-operations/comment-page-1/#comment-351231</link>
		<dc:creator>Pat</dc:creator>
		<pubDate>Tue, 02 Sep 2008 14:30:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=482#comment-351231</guid>
		<description>Another thing worth pointing out is the check the latency of your network connections as well as the throughput. A high throughput high latency link can often give you worse performance (despite the high throughput) than a narrow pipe without latency problems.

Especially if you app makes a lot of very fast queries, you may find network round trip takes longer than actual query execution.</description>
		<content:encoded><![CDATA[<p>Another thing worth pointing out is the check the latency of your network connections as well as the throughput. A high throughput high latency link can often give you worse performance (despite the high throughput) than a narrow pipe without latency problems.</p>
<p>Especially if you app makes a lot of very fast queries, you may find network round trip takes longer than actual query execution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: peter</title>
		<link>http://www.mysqlperformanceblog.com/2008/09/01/how-network-can-impact-mysql-operations/comment-page-1/#comment-351068</link>
		<dc:creator>peter</dc:creator>
		<pubDate>Tue, 02 Sep 2008 04:46:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=482#comment-351068</guid>
		<description>Bill, 

Sure you want network to be working normally.  I would watch error rate on switches as well as on local nodes and on local network traffic you should expect it to be close to zero. If it is not something may be faulty or miss-configured.</description>
		<content:encoded><![CDATA[<p>Bill, </p>
<p>Sure you want network to be working normally.  I would watch error rate on switches as well as on local nodes and on local network traffic you should expect it to be close to zero. If it is not something may be faulty or miss-configured.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Karwin</title>
		<link>http://www.mysqlperformanceblog.com/2008/09/01/how-network-can-impact-mysql-operations/comment-page-1/#comment-350931</link>
		<dc:creator>Bill Karwin</dc:creator>
		<pubDate>Mon, 01 Sep 2008 17:38:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=482#comment-350931</guid>
		<description>Just to correct myself:  those anecdotes apply to stranded coaxial network cables, not CAT5.</description>
		<content:encoded><![CDATA[<p>Just to correct myself:  those anecdotes apply to stranded coaxial network cables, not CAT5.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill Karwin</title>
		<link>http://www.mysqlperformanceblog.com/2008/09/01/how-network-can-impact-mysql-operations/comment-page-1/#comment-350929</link>
		<dc:creator>Bill Karwin</dc:creator>
		<pubDate>Mon, 01 Sep 2008 17:28:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/?p=482#comment-350929</guid>
		<description>Another network-level performance concern is faulty cables.  When I worked in tech support for InterBase, we helped customers whose performance problems were solved when they replaced the CAT5 cables between their app server and database server.  

Cables contain tiny copper filaments, and these get metal fatigue if they are bent too frequently.  If too many filaments are broken this way, the cable can become faulty.  TCP is designed to re-try packets that aren&#039;t transmitted reliably, but that cuts down on throughput.  

We helped a customer who had up to 90% packet loss (which means each packet needs to be re-sent up to 10 times) because of his old, damaged cables.</description>
		<content:encoded><![CDATA[<p>Another network-level performance concern is faulty cables.  When I worked in tech support for InterBase, we helped customers whose performance problems were solved when they replaced the CAT5 cables between their app server and database server.  </p>
<p>Cables contain tiny copper filaments, and these get metal fatigue if they are bent too frequently.  If too many filaments are broken this way, the cable can become faulty.  TCP is designed to re-try packets that aren&#8217;t transmitted reliably, but that cuts down on throughput.  </p>
<p>We helped a customer who had up to 90% packet loss (which means each packet needs to be re-sent up to 10 times) because of his old, damaged cables.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
