What size page are you using (ie. how many results per query)? A: 10
When you said the results would sometimes take three minutes, is that per page, or to paginate through all of the results? A: I don't observe any difference by paging the first or any next page. That wait time is only when I start riak and run the first request (whatever that request is, paging, key lookup, or just getting a reference to a bucket). Are you observing CPU and memory utilization while these stalls happen? A: Yes, I see both CPU and memory but nothing above 50% of use. If I do bucket.keys (yes, not recommended) then it's the only way I get my CPU usage close to 100%. I don't do that as part of my benchmarking. I did it a couple times just to see it happening, and actually none of these times took riak down. Do you have swap disabled? A: Nope. Why you would recommend doing so? Could there be any downsides? On Wed, Sep 25, 2013 at 2:18 PM, Reid Draper <reiddra...@gmail.com> wrote: > > On Sep 25, 2013, at 3:39 PM, Wagner Camarao <wag...@crunchbase.com> wrote: > > Reid, > Thanks for bringing that up and yes I'm using paginated 2i. > > > * What size page are you using (ie. how many results per query)? > * When you said the results would sometimes take three minutes, is that > per page, or to paginate through all of the results? > * Are you observing CPU and memory utilization while these stalls happen? > * Do you have swap disabled? > > Reid > >
_______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
