QnaList > Groups > Project-Voldemort > Mar 2016
faq

[project-voldemort] Thing Cluster For Large Value

Hi
My cluster average put & get size is 90KB.  I am running on SSD based 
server and have 60 GB of jvm setting.  I setting db.cache.evictln�lse.
Is there any other setting that I need to change to optimize my puts ?
If anyone tried earlier and played with various settings?
Thanks
Mital
You received this message because you are subscribed to the Google Groups "project-voldemort" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
Visit this group at https://groups.google.com/group/project-voldemort.
For more options, visit https://groups.google.com/d/optout.

asked Mar 8 2016 at 13:57

Mital Parmar 's gravatar image



2 Replies for : [project-voldemort] Thing Cluster For Large Value
What is the latency you are getting for writes ? What version are you using
We generally run with bdb.cache.evictln=true to get better performance.
Please read through the following to see what other settings you can try on.
https://github.com/voldemort/voldemort/blob/master/bin/PREUPGRADE_FOR_1_1_X_README
Ability to move data off disk. This is very GC friendly, relying on OS page
   cache for the data and using the JVM heap only for index. This is
achieved
   by setting "bdb.cache.evictln" server parameter to "true"
impact
   on online traffic (Restore, Rebalance, Retention). This is achieved by
   setting "bdb.minimize.scan.impact" to "true"
cost
   of an additional delete()
Thanks,
Arun.
You received this message because you are subscribed to the Google Groups "project-voldemort" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
Visit this group at https://groups.google.com/group/project-voldemort.
For more options, visit https://groups.google.com/d/optout.

answered Mar 8 2016 at 15:15

Arunachalam 's gravatar image


Mital,
Like Arun said, you should set bdb.cache.evictln=true. Setting it to false 
is an optimization for slow spinning disks at the cost of increased JVM 
heap usage (and consequently longer GC times), but you're on SSD. So, 
you'll actually have better performance if you set this to true.
Can you also give us more details on your read and write patterns?
- put() per second
- get() per second
- getAll() per second
- delete() per second
- For pu(), ratio of updates versus creates (overwrite versus new key)
- For getAll(), average and max number of keys per call
- Average and max key size
- Average and max value size
- How many stores on the cluster
You're best off making the JVM as small as possible, but you will need to 
have enough bdb cache to hold the hotset of the indexes of the stores.
A quick performance enhancement out of the box is to remove the 
ReadOnlyStorageEngineConfiguration from the storage.configs parameter. That 
way you only have the BdbStorageEngine running in your app.
This is one of our cluster configurations that hosts 50 stores and gets 
about a peak of 70,000 writes a second against billions of keys:
admin.max.threads@
bdb.cache.evictln=true
bdb.cache.size GB
bdb.checkpoint.interval.bytes!47483648
bdb.cleaner.interval.bytes728640
bdb.cleaner.lazy.migration�lse
bdb.cleaner.min.file.utilization=0
bdb.cleaner.threads=1
bdb.enable=true
bdb.evict.by.level=true
bdb.expose.space.utilization=true
bdb.lock.nLockTablesG
bdb.minimize.scan.impact=true
bdb.one.env.per.store=true
bdb.raw.property.string=je.cleaner.adjustUtilization�lse
data.directory=${voldemort.data.dir}
enable.server.routing�lse
enable.verbose.logging�lse
http.enable�lse
max.proxy.put.threadsP
nio.connector.selectorsP
num.scan.permits=2
restore.data.timeout.sec14000
retention.cleanup.first.start.hour=3
scheduler.threads$
slop.frequency.ms`0000
storage.configs=voldemort.store.bdb.BdbStorageConfiguration
stream.read.byte.per.sec 9715200
stream.write.byte.per.secx643200
voldemort.home=${voldemort.home.dir}
Some of the settings, 
like bdb.cleaner.threads, bdb.checkpoint.interval.bytes and 
bdb.cleaner.interval.bytes depend heavily on how frequently you create new 
keys and overwrite existing keys and how large the average and peak write 
sizes are.
We host that config in a 31gb Xms/Xmx JVM heap with UseCompressedOops set.
You received this message because you are subscribed to the Google Groups "project-voldemort" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
Visit this group at https://groups.google.com/group/project-voldemort.
For more options, visit https://groups.google.com/d/optout.

answered Mar 8 2016 at 18:44

Brendan Harris (a.k.a. stotch on irc.oftc.net) 's gravatar image


Related discussions

Tagged

Group Project-voldemort

asked Mar 8 2016 at 13:57

active Mar 8 2016 at 18:44

posts:3

users:3

Project-voldemort

©2013 QnaList.com