slimina / xmemcached

Automatically exported from code.google.com/p/xmemcached
Apache License 2.0
0 stars 0 forks source link

Performance issue with net.rubyeye.xmemcached.transcoders.SerializingTranscoder:decode #184

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start memcached server with 8G memory on a remote server
2. Perform consistent 'gets' and 'sets' 
3. Client being used is Xmemcached

What is the expected output? What do you see instead?
net.rubyeye.xmemcached.transcoders.SerializingTranscoder:decode is taking 
>300ms. The time it takes should be in the order of tens of milliseconds.

What version of the product are you using? On what operating system?
1.3.2

Please provide any additional information below.

Original issue reported on code.google.com by rohan.ra...@gmail.com on 19 Mar 2012 at 2:50

Attachments:

GoogleCodeExporter commented 9 years ago
What's the size of your data? And what's your transcoder compress threshold?

I think the time was spent on data compression.

Original comment by killme2...@gmail.com on 19 Mar 2012 at 2:55

GoogleCodeExporter commented 9 years ago
Thanks for your quick reply. 
Is there any direct method of knowing the size of my data? 

Also, transcoder compress threshold is set to default. We are not setting any 
value externally. If we had to set it, what would be a good value?

Thanks in advance!

Original comment by rohan.ra...@gmail.com on 19 Mar 2012 at 3:29

GoogleCodeExporter commented 9 years ago
You can use 'stats sizes' by telnet to get an approximate size of the item.

Original comment by killme2...@gmail.com on 19 Mar 2012 at 3:39

GoogleCodeExporter commented 9 years ago
'stats sizes' on the telnet interface gives me this

stats sizes
STAT 201152 1
END

Based on this, what would be the ideal 'transcoder compress threshold' ?

Thanks you so much for looking into this

Original comment by rohan.ra...@gmail.com on 19 Mar 2012 at 5:34