Index Design Question

Luke Bakken lbakken at
Mon Mar 28 13:10:00 EDT 2016

Hi Joe,

In order to provide the best answer, example (dummy) data and a
description of how the index will be queried would help a lot.


Luke Bakken
lbakken at

On Wed, Mar 23, 2016 at 10:01 AM, Joe Olson <technology at> wrote:
> Index design question....
> Suppose I have N customers I am tracking data for. All customer data is
> basically the same structure, and I have determined I need a simple
> secondary index on this data in order to satisfy a business goal.
> Is it better to have N indexes (N ~ 100), or a single index, with the
> customer ID the most significant part of a compound index?
> Assume the app will not access all customers equally, some customers data
> will be accessed far more frequently than others.
> I tend to think a one giant index is more susceptible to failure, and I'm
> not sure how the caching and swapping to disk is affected under each
> scenario.
> Any thoughts? Target clusters size is 7 nodes., 16GB ram each. If N indexes
> is workable, how high can N be?
> Thanks!
> _______________________________________________
> riak-users mailing list
> riak-users at

More information about the riak-users mailing list