Performance problem: put operation takes seconds

Christian Dahlqvist christian at basho.com
Mon Jul 22 09:54:17 EDT 2013


Hi,

A reasonably common cause for sudden spikes in latencies is that the buffers used for internal communication gets exhausted. This tends to manifest itself through large number of 'busy_dist_port' messages in the logs. This is especially common if you have large objects or objects with lots of small siblings.

Check your logs to see if you see any busy_dist_port messages in the console logs. If this is the case, add the following line to the vm.args file:

+zdbbl 16384

This increases the default buffer size to 16MB, but may need to be increased further depending on the size distribution of your data.

Also monitor statistics to see if you have large objects (node_get_fsm_objsize_100) and/or lots of siblings (node_get_fsm_siblings_100). Ideally try to keep object size below 4-5MB and ensure that your application resolves siblings if have this enabled, as it otherwise can cause objects to grow uncontrollably.

Best regards,

Christian



On 22 Jul 2013, at 14:10, ks <ksafonov at rutarget.ru> wrote:

> Hi Christian!
> 
> Sure:
> vm.args <http://riak-users.197444.n3.nabble.com/file/n4028480/vm.args>  
> app.config <http://riak-users.197444.n3.nabble.com/file/n4028480/app.config>  
> 
> Thanks!
> ks
> 
> 
> 
> --
> View this message in context: http://riak-users.197444.n3.nabble.com/Performance-problem-put-operation-takes-seconds-tp4028478p4028480.html
> Sent from the Riak Users mailing list archive at Nabble.com.
> 
> _______________________________________________
> riak-users mailing list
> riak-users at lists.basho.com
> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com





More information about the riak-users mailing list