mbbroberg/Conclusion of thread

## Conclusion of thread
Hey Santi, Baskar,

Are you noticing increased CPU load as you create more and more indexes? Running `riak-admin top -interval 2` a few times may bring sometime to light.

I’d see how you could increase resources or think more critically on how you’re indexing data for Solr. Does the data share most fields? Can you reuse indexes for some of the data and filter certain queries?

You may also wanted to look at this thread, https://groups.google.com/forum/#!topic/nosql-databases/9ECQpVS0QjE, which discusses modeling Riak Search data and the issues you’ll have with the overhead with gossiping so much metadata and the what Solr can handle.

Zeeshan Lakhani
programmer |
software engineer at @basho |
org. member/founder of @papers_we_love | paperswelove.org
twitter => @zeeshanlakhani
------------------------------------------------------------------------------------------------------------------
Hello Zeeshan,

We create a new set of buckets/indices when a new tenant is created in a multi-tenancy environment. Alternate approach for us is to use single set of index/buckets and filter by a tenant identifier. Before moving to the second approach we want to confirm if we expect to see significant delays (several minutes) with index propagation as the number of indices in the system grows.

Regards,
Baskar
------------------------------------------------------------------------------------------------------------------
The second approach would most probably cut down on index creation time. However, you should definitely spend a little time testing it out and benchmarking accordingly. And, as I mentioned, please take a look at CPU load  as indexes are created, as well as experiment with solrconfig and increasing jvm heap memory settings for your use-case.

Thanks.

Zeeshan Lakhani
programmer |
software engineer at @basho |
org. member/founder of @papers_we_love | paperswelove.org
twitter => @zeeshanlakhani
	Hey Santi, Baskar,

	Are you noticing increased CPU load as you create more and more indexes? Running `riak-admin top -interval 2` a few times may bring sometime to light.

	I’d see how you could increase resources or think more critically on how you’re indexing data for Solr. Does the data share most fields? Can you reuse indexes for some of the data and filter certain queries?

	You may also wanted to look at this thread, https://groups.google.com/forum/#!topic/nosql-databases/9ECQpVS0QjE, which discusses modeling Riak Search data and the issues you’ll have with the overhead with gossiping so much metadata and the what Solr can handle.

	Zeeshan Lakhani
	programmer \|
	software engineer at @basho \|
	org. member/founder of @papers_we_love \| paperswelove.org
	twitter => @zeeshanlakhani
	------------------------------------------------------------------------------------------------------------------
	Hello Zeeshan,

	We create a new set of buckets/indices when a new tenant is created in a multi-tenancy environment. Alternate approach for us is to use single set of index/buckets and filter by a tenant identifier. Before moving to the second approach we want to confirm if we expect to see significant delays (several minutes) with index propagation as the number of indices in the system grows.

	Regards,
	Baskar
	------------------------------------------------------------------------------------------------------------------
	The second approach would most probably cut down on index creation time. However, you should definitely spend a little time testing it out and benchmarking accordingly. And, as I mentioned, please take a look at CPU load as indexes are created, as well as experiment with solrconfig and increasing jvm heap memory settings for your use-case.

	Thanks.

	Zeeshan Lakhani
	programmer \|
	software engineer at @basho \|
	org. member/founder of @papers_we_love \| paperswelove.org
	twitter => @zeeshanlakhani