Drizzleslap timeout error

Bug #684269 reported by Vijay Samuel
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Drizzle
Fix Released
Medium
Andrew Hutchings
7.0
Fix Released
Medium
Andrew Hutchings

Bug Description

Drizzleslap times out for some reason on my box but its fine on our servers.

Related branches

Vijay Samuel (vjsamuel)
Changed in drizzle:
assignee: nobody → Andrew Hutchings (linuxjedi)
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

Can you please paste the output for the timeout, and if possible the logs dtr generates?

Changed in drizzle:
status: Triaged → Incomplete
Revision history for this message
Patrick Crews (patrick-crews) wrote :

I have been seeing this on my laptop as well. From checking the processlist, it looks like drizzleslap is running during the test, but the test is just taking too long (DTR will timeout after some preset time if a case takes too long).

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

reproduced locally

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

Trunk 1965:

[linuxjedi@linuxjedi-laptop drizzle-trunk]$ bin/drizzleslap --concurrency=5 --iterations=20 --number-int-cols=2 --number-char-cols=3 --auto-generate-sql --create-schema=test_env --auto-generate-sql-add-autoincrement --commit=100
Benchmark
 Load: mixed
 Average Time took to generate schema and initial data: 10.671 seconds
 Average number of seconds to run all queries: 0.229 seconds
 Minimum number of seconds to run all queries: 0.108 seconds
 Maximum number of seconds to run all queries: 0.442 seconds
 Total time for tests: 4.595 seconds
 Standard Deviation: 0.093
 Number of queries in create queries: 102
 Number of clients running queries: 5/5
 Number of times test was run: 20
 Average number of queries per client: 0

Trunk 1952:

[linuxjedi@linuxjedi-laptop drizzle-trunk]$ bin/drizzleslap --concurrency=5 --iterations=20 --number-int-cols=2 --number-char-cols=3 --auto-generate-sql --create-schema=test_env --auto-generate-sql-add-autoincrement --commit=100 --port=4428
Benchmark
 Load: mixed
 Average Time took to generate schema and initial data: 5.708 seconds
 Average number of seconds to run all queries: 0.107 seconds
 Minimum number of seconds to run all queries: 0.091 seconds
 Maximum number of seconds to run all queries: 0.158 seconds
 Total time for tests: 2.147 seconds
 Standard Deviation: 0.013
 Number of queries in create queries: 102
 Number of clients running queries: 5/5
 Number of times test was run: 20
 Average number of queries per client: 0

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

Regression introduced in revision 1955 (InnoDB 1.1.1)

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

Also InnoDB 1.1.2 branch has a further 10% regression

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

Awaiting InnoDB 1.1.3. There are some excessive IO fixes in it which should solve this.

Revision history for this message
Stewart Smith (stewart) wrote :

workaround: use libeatmydata

Revision history for this message
Andrew Hutchings (linuxjedi) wrote :

Results with InnoDB 1.1.3:

 Average Time took to generate schema and initial data: 5.926 seconds
 Average number of seconds to run all queries: 0.117 seconds
 Minimum number of seconds to run all queries: 0.100 seconds
 Maximum number of seconds to run all queries: 0.242 seconds
 Total time for tests: 2.349 seconds
 Standard Deviation: 0.031
 Number of queries in create queries: 102
 Number of clients running queries: 5/5
 Number of times test was run: 20
 Average number of queries per client: 0

That fixed it :)

Revision history for this message
Vijay Samuel (vjsamuel) wrote : Re: [Bug 684269] Re: Drizzleslap timeout error

Thats awesome! :)
Cheers!
 -Vijay
On Tue, Dec 7, 2010 at 9:50 PM, Andrew Hutchings
<email address hidden>wrote:

> Results with InnoDB 1.1.3:
>
> Average Time took to generate schema and initial data: 5.926 seconds
> Average number of seconds to run all queries: 0.117 seconds
> Minimum number of seconds to run all queries: 0.100 seconds
> Maximum number of seconds to run all queries: 0.242 seconds
> Total time for tests: 2.349 seconds
> Standard Deviation: 0.031
> Number of queries in create queries: 102
> Number of clients running queries: 5/5
> Number of times test was run: 20
> Average number of queries per client: 0
>
>
> That fixed it :)
>
> ** Branch linked: lp:~stewart/drizzle/update-innobase-1.1.3
>
> ** Changed in: drizzle/elliott
> Status: Triaged => Fix Committed
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/684269
>
> Title:
> Drizzleslap timeout error
>
> Status in A Lightweight SQL Database for Cloud Infrastructure and Web
> Applications:
> Fix Committed
> Status in Drizzle elliott series:
> Fix Committed
>
> Bug description:
> Drizzleslap times out for some reason on my box but its fine on our
> servers.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/drizzle/+bug/684269/+subscribe
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.