Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Performance tuning the MySQL persistence store
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  5 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Travis Bear  
View profile  
 More options Mar 16 2011, 9:54 pm
From: Travis Bear <travis.b...@gmail.com>
Date: Wed, 16 Mar 2011 18:54:42 -0700 (PDT)
Local: Wed, Mar 16 2011 9:54 pm
Subject: Performance tuning the MySQL persistence store
Hi,

In my test Voldemort cluster (running version 0.81) I've been
experimenting with getting better Voldemort performance when using
MySQL for persistence, and a couple of questions have come up:

Is there any way to configure the number of JDBC connections between
Voldemort and MySQL?  We have 16 CPU's available, but our MySQL
monitoring tools only show 8 active connections.  I've searched the
documentation and Google for information, but found no information on
how to increase this.

I'd also like to know if there are any options for Voldemort to cache
or re-use precompiled SQL statements?  Our MySQL monitoring currently
doesn't show this happening.

Thanks!

-Travis


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Travis Bear  
View profile  
 More options Mar 18 2011, 3:16 pm
From: Travis Bear <travis.b...@gmail.com>
Date: Fri, 18 Mar 2011 12:16:53 -0700 (PDT)
Local: Fri, Mar 18 2011 3:16 pm
Subject: Re: Performance tuning the MySQL persistence store
Just to answer my own question:  I resolved this issue by making
changes to voldemort.store.mysql.MysqlStorageConfiguration, where I
was able to set the specific parameters to the Apache commons
Datasource that I wanted.  By customizing these settings I was able to
coax 50% more throughput out of Voldemort.

If there is interest in these changes, I can submit a patch that
exposes these settings as config options.

-Travis

On Mar 16, 6:54 pm, Travis Bear <travis.b...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Liam Slusser  
View profile  
 More options Mar 19 2011, 3:01 am
From: Liam Slusser <lslus...@gmail.com>
Date: Sat, 19 Mar 2011 00:01:26 -0700
Local: Sat, Mar 19 2011 3:01 am
Subject: Re: [project-voldemort] Re: Performance tuning the MySQL persistence store
I am interested in your configuration changes you made...why don't you
post them here?  How does the performance compare with bdb?

thanks,
liam


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Travis Bear  
View profile  
 More options Mar 21 2011, 6:02 pm
From: Travis Bear <travis.b...@gmail.com>
Date: Mon, 21 Mar 2011 15:02:33 -0700 (PDT)
Local: Mon, Mar 21 2011 6:02 pm
Subject: Re: Performance tuning the MySQL persistence store
Liam,

I put a custom version of Voldemort on GitHub that exposes several of
the Apache Commons DBCP settings as config options in Voldemort's
server.properties file.

https://github.com/travis-bear/voldemort/tree/mysql/dbcpParams

(note that the branch is 'mysql/dbcpParams', not 'master')

Here is a list of the new properties that are settable, plus some
sample values that seem to work well on our hardware.

mysql.ds.initialPoolSize=16
mysql.ds.poolPreparedStatements=true
mysql.ds.maxActiveConnections=16
mysql.ds.minIdleConnections=8

Some performance numbers from our own environment:

standard Voldemort on the Percona version of MySQL: 12k max TPS
custom Voldemort on Percona/MySQL with the config settings above: 20k
max TPS
standard Voldemort on BDB: 30k max TPS

Any questions, let me know.

-Travis

On Mar 19, 12:01 am, Liam Slusser <lslus...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Sunny Gleason  
View profile  
 More options Mar 21 2011, 6:27 pm
From: Sunny Gleason <sunny.glea...@gmail.com>
Date: Mon, 21 Mar 2011 18:27:59 -0400
Local: Mon, Mar 21 2011 6:27 pm
Subject: Re: [project-voldemort] Re: Performance tuning the MySQL persistence store
Hi Travis,

Great stuff -- one question, how far out did you test? (In
terms of time, records inserted, size of DB in GB esp. in
relation to size of available RAM?)

The reason I ask is that when I was benchmarking bdb, I
found that performance fell to 25% of initial performance
within 900 seconds of continuous insertion. (Once the
data didn't fit in RAM anymore...)

(see slide 32+ here for graphs of the performance)...
http://slideshare.net/sunnygleason/accelerating-nosql

Thank you for sharing! This is very interesting work--

-Sunny

On 3/21/11, Travis Bear <travis.b...@gmail.com> wrote:


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »