<?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: MyISAM concurrent insert</title>
	<atom:link href="http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/</link>
	<description>Percona&#039;s MySQL &#38; InnoDB performance and scalability blog</description>
	<lastBuildDate>Sat, 11 Feb 2012 16:45:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Richard</title>
		<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/comment-page-1/#comment-815378</link>
		<dc:creator>Richard</dc:creator>
		<pubDate>Tue, 23 Aug 2011 13:44:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/#comment-815378</guid>
		<description>OK, I&#039;ve never mucked much with this setting, or ever actually, but the stock site I manage is about 170 gig on drive, daily does millions of inserts, updates, selects, and a few 1000 deletes. Some of the larger tables are well over 100,000,000 rows of data, that are part of the daily changes.  I have noticed since more and more data is being written, changed, I&#039;m getting slow query issues reading and writing.  Do you think if I were to disabled concurrent insert this would help or worsen the select from time issues (the tables are Primary Key index ID,Date, and indexed Date, with the Select statements always:

Select from table where ID = ###### Order by Date

with sometimes

AND  Date &gt;= 20100101 and Date &lt;= 20110101 (for ranges of between specific dates)</description>
		<content:encoded><![CDATA[<p>OK, I&#8217;ve never mucked much with this setting, or ever actually, but the stock site I manage is about 170 gig on drive, daily does millions of inserts, updates, selects, and a few 1000 deletes. Some of the larger tables are well over 100,000,000 rows of data, that are part of the daily changes.  I have noticed since more and more data is being written, changed, I&#8217;m getting slow query issues reading and writing.  Do you think if I were to disabled concurrent insert this would help or worsen the select from time issues (the tables are Primary Key index ID,Date, and indexed Date, with the Select statements always:</p>
<p>Select from table where ID = ###### Order by Date</p>
<p>with sometimes</p>
<p>AND  Date &gt;= 20100101 and Date &lt;= 20110101 (for ranges of between specific dates)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bandara</title>
		<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/comment-page-1/#comment-699413</link>
		<dc:creator>Bandara</dc:creator>
		<pubDate>Mon, 21 Dec 2009 18:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/#comment-699413</guid>
		<description>Hi,

Any one know how to run mySQL from the visual studio 2008. I tried by building the mySQL source code and it worked fine. But problem is how to run it. So if any one can provide step by step procedure its great.</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Any one know how to run mySQL from the visual studio 2008. I tried by building the mySQL source code and it worked fine. But problem is how to run it. So if any one can provide step by step procedure its great.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Marc Pinel</title>
		<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/comment-page-1/#comment-337964</link>
		<dc:creator>Marc Pinel</dc:creator>
		<pubDate>Thu, 31 Jul 2008 15:01:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/#comment-337964</guid>
		<description>Hi man,

i have concurrent-insert=2 set....how would the positively impact the performance? i have a torrent tracker (legal content ofcourse) with heavy php and mysql visits daily...and some spikes.</description>
		<content:encoded><![CDATA[<p>Hi man,</p>
<p>i have concurrent-insert=2 set&#8230;.how would the positively impact the performance? i have a torrent tracker (legal content ofcourse) with heavy php and mysql visits daily&#8230;and some spikes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Online Car Insurance Rate Quotes</title>
		<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/comment-page-1/#comment-2865</link>
		<dc:creator>Online Car Insurance Rate Quotes</dc:creator>
		<pubDate>Thu, 28 Sep 2006 07:36:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/#comment-2865</guid>
		<description>&lt;strong&gt;Online Car Insurance Rate Quotes...&lt;/strong&gt;

Online Car Insurance Rate Quotes...</description>
		<content:encoded><![CDATA[<p><strong>Online Car Insurance Rate Quotes&#8230;</strong></p>
<p>Online Car Insurance Rate Quotes&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadim</title>
		<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/comment-page-1/#comment-2766</link>
		<dc:creator>Vadim</dc:creator>
		<pubDate>Mon, 25 Sep 2006 06:16:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/#comment-2766</guid>
		<description>Jerry,

Well...
There are several points:
1. Possible negative effect - your INSERTS will be a bit longer. I don&#039;t know any bugs with disabled concurrent insert.
2. If you use only point selects, or selects that retieve only several rows - I don&#039;t think concurrent=off will help you much - perhaps otherwise.
3. if you use select retrieves many rows - you definitely should use concurrent=off
4. if your database is more write that read - then I again don&#039;t think concurrent is important for you - most time
tables are in WRITE lock.
5. But better way - test it - for example you can take mysql with patched query log and analyze execution time of queries with concurrent insert = off and on.</description>
		<content:encoded><![CDATA[<p>Jerry,</p>
<p>Well&#8230;<br />
There are several points:<br />
1. Possible negative effect &#8211; your INSERTS will be a bit longer. I don&#8217;t know any bugs with disabled concurrent insert.<br />
2. If you use only point selects, or selects that retieve only several rows &#8211; I don&#8217;t think concurrent=off will help you much &#8211; perhaps otherwise.<br />
3. if you use select retrieves many rows &#8211; you definitely should use concurrent=off<br />
4. if your database is more write that read &#8211; then I again don&#8217;t think concurrent is important for you &#8211; most time<br />
tables are in WRITE lock.<br />
5. But better way &#8211; test it &#8211; for example you can take mysql with patched query log and analyze execution time of queries with concurrent insert = off and on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jerry</title>
		<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/comment-page-1/#comment-2756</link>
		<dc:creator>Jerry</dc:creator>
		<pubDate>Sun, 24 Sep 2006 16:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/#comment-2756</guid>
		<description>What is the negative impact to turn the concurrent_insert off? Will it make insert waits much longer? Is there any bug or issue related to turn off this default feature?
Will turning off the feature help queries which have no insert on the same table at the same time?

My system has update:Insert:Select ratio is 3:1.5:1 so the db is write more than read.

Thanks.</description>
		<content:encoded><![CDATA[<p>What is the negative impact to turn the concurrent_insert off? Will it make insert waits much longer? Is there any bug or issue related to turn off this default feature?<br />
Will turning off the feature help queries which have no insert on the same table at the same time?</p>
<p>My system has update:Insert:Select ratio is 3:1.5:1 so the db is write more than read.</p>
<p>Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadim</title>
		<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/comment-page-1/#comment-260</link>
		<dc:creator>Vadim</dc:creator>
		<pubDate>Fri, 23 Jun 2006 13:31:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/#comment-260</guid>
		<description>Citrin,

I usually use sysbench (http://sysbench.sf.net).</description>
		<content:encoded><![CDATA[<p>Citrin,</p>
<p>I usually use sysbench (<a href="http://sysbench.sf.net" rel="nofollow">http://sysbench.sf.net</a>).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: citrin</title>
		<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/comment-page-1/#comment-259</link>
		<dc:creator>citrin</dc:creator>
		<pubDate>Fri, 23 Jun 2006 13:22:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/#comment-259</guid>
		<description>Which soft was used in this benchmark?</description>
		<content:encoded><![CDATA[<p>Which soft was used in this benchmark?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vadim</title>
		<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/comment-page-1/#comment-194</link>
		<dc:creator>Vadim</dc:creator>
		<pubDate>Sat, 17 Jun 2006 05:15:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/#comment-194</guid>
		<description>I did not test concurrent-insert = 2, but looking at source code - it changes SELECTs code in no way. So the results will be the same.</description>
		<content:encoded><![CDATA[<p>I did not test concurrent-insert = 2, but looking at source code &#8211; it changes SELECTs code in no way. So the results will be the same.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apachez</title>
		<link>http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/comment-page-1/#comment-187</link>
		<dc:creator>Apachez</dc:creator>
		<pubDate>Fri, 16 Jun 2006 21:26:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.mysqlperformanceblog.com/2006/06/13/myisam-concurrent-insert/#comment-187</guid>
		<description>How does the &quot;concurrent-insert = 2&quot; feature described by Arjen affect the outcome of the above benchmark ?</description>
		<content:encoded><![CDATA[<p>How does the &#8220;concurrent-insert = 2&#8243; feature described by Arjen affect the outcome of the above benchmark ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

