Great work Biping!

I'm very interested to see how things scale out with read-write
workloads and mixed workloads. I can also help you run some of these
tests on larger 16 core machines if you don't have access to any.

Thanks!
-Eric

On Thu, Jul 30, 2009 at 09:49:45AM +0800, Biping MENG wrote:
>    On Thu, Jul 30, 2009 at 1:03 AM, Jay Pipes <[email protected]> wrote:
> 
>      Biping MENG wrote:
> 
>        Unsolved problems:
>          Actually I ran the "readwrite" series of sysbenches as well. But
>        encountered errors at concurrency level of 2048. So the result is not
>        complete for "readwrite".  
> 
>      Don't run readwrites on InnoDB with concurrency levels greater than
>      1024.  There is a hard limit of 1024 transactions in the concurrent lock
>      graph currently and deadlocks and undefined behaviour are known to occur
>      when concurrency exceeds 1024.  This is a known issue that Oracle (or
>      maybe Percona?) has developed a beta solution for and hopefully will
>      find its way into the next plugin version, at which point Drizzle will
>      of course pull in the improvements.
> 
>    ah, I guess it is the famous InnoDB 1024 bug? 
>    Thanks for your explanation about it!
>    I'm just making up this part of readwrite test. And will be posting it to
>    this thread right after I got results:)
>     
> 
>      Cheers!
>      jay
> 
>    --
>    Cheers.
> 
>    Biping MENG

_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help   : https://help.launchpad.net/ListHelp

Reply via email to