ad-before-write slow down new writes so much?
>>
>> Some new information we've found - it seems that if we write the data and
>> then update it, we get fast speeds too. It's just the initial write of the
>> data that is slow.
>>
>> So why is writing sequential
keys?
>
>
>
> --
> View this message in context:
> http://riak-users.197444.n3.nabble.com/How-to-increase-Riak-write-performance-for-sequential-alpha-numeric-keys-tp4034219p4034225.html
> Sent from the Riak Users mailing list archive at Nabble.com.
>
>
and throttles on the Riak servers and windows API servers.
>
> As a kicker, if we reverse the keys e.g.
>
> 100~1~1~0391~CSU
>
> speed goes up to over *3000 rows*, but that's a dirty kludge.
>
> Can anyone explain why Riak doesn't like sequential alpha-numeri
keys so much slower than updating them or
> writing non-sequential keys?
>
>
>
> --
> View this message in context:
> http://riak-users.197444.n3.nabble.com/How-to-increase-Riak-write-performance-for-sequential-alpha-numeric-k
gt; data that is slow.
>
> So why is writing sequential keys so much slower than updating them or
> writing non-sequential keys?
>
>
>
> --
> View this message in context:
> http://riak-users.197444.n3.nabble.com/How-to-increase-Riak-write-performance-for-sequential-alpha-num
.nabble.com/How-to-increase-Riak-write-performance-for-sequential-alpha-numeric-keys-tp4034219p4034225.html
Sent from the Riak Users mailing list archive at Nabble.com.
___
riak-users mailing list
riak-users@lists.basho.com
http://lists.basho.com/mailman
On 5 May 2016, at 14:42, Sanket Agrawal wrote:
>
> On Thu, May 5, 2016 at 9:28 AM, Russell Brown wrote:
> CRDTs are all about mutation, why would you use a CRDT for immutable data? I
> think write-once is what you need.
>
> No particular
On Thu, May 5, 2016 at 9:28 AM, Russell Brown wrote:
> CRDTs are all about mutation, why would you use a CRDT for immutable data?
> I think write-once is what you need.
No particular reason - most likely ignorance on my part, I think :) Basho
documentation mentioned
ak servers we've set the ulimit to:
>>
>>
>> riak soft nofile 32768
>> riak hard nofile 65536
>>
>>
>> and other settings like this:
>>
>>
>> ring_size = 128
>> protobuf.backlog = 1024
>> anti_entropy = passive
>>
>>
gt; an API on 3 machines.
>
> We've checked all the usual bottlenecks: CPU, memory, network IO, disk IO
> and throttles on the Riak servers and windows API servers.
>
> As a kicker, if we reverse the keys e.g.
>
> 100~1~00001~0391~CSU
>
> speed goes up to over *3000 ro
and
what we can change to improve performance?
Thanks!
--
View this message in context:
http://riak-users.197444.n3.nabble.com/How-to-increase-Riak-write-performance-for-sequential-alpha-numeric-keys-tp4034219.html
Sent from the Riak Users mailing list archive at Nabble.com.___
11 matches
Mail list logo