tuning riak for 100s of concurrent connections

Wilson MacGyver wmacgyver at gmail.com
Fri Feb 25 14:57:13 EST 2011


It's not an actual use case. the actual use case is in fact fairly
random access pattern to
the keys.

it's however a 6 node system, with 3 copies. I'd assume riak can cope with this.

I'd also figure the OS level cache would cache the bitcask chunk pretty quickly.

On Fri, Feb 25, 2011 at 2:38 PM, Ryan Zezeski <rzezeski at gmail.com> wrote:
>
>
> On Fri, Feb 25, 2011 at 12:45 PM, Wilson MacGyver <wmacgyver at gmail.com>
> wrote:
>>
>>  I purposely have it grab the same key/value over and over
>> again.
>>
>
> Could the fact that your getting the same key for each request also be a
> factor here?  Wouldn't this mean high contention on those vnodes?  Is this
> an actual use case?
> -Ryan
>



-- 
Omnem crede diem tibi diluxisse supremum.




More information about the riak-users mailing list