Home | Forums | Couchbase | Couchbase Server 1.8.x

Benefits of Clustering

1 reply [Last post]
Thu, 05/31/2012 - 19:14
garazy
Offline
Joined: 05/31/2012
Groups: None

Hi,

I'm new to Couchbase but so far it's been great although it's early days. Previously I was using SQL Server as a key/value store and today it just became unusable.

Setup -

Dedicated database server with 22.9GB allocated to Couchbase.

I'm doing about 4 creates per second and 11 gets per second, the creates will slow and the gets increasing once the item count reaches about 10 million. The actual items themselves are just a datetime and an array of between 10 and 30 guids.

The data isn't actually that important (If it gets deleted its no big deal and I've disabled replication), what's more important is speed to access the data. I was wondering if anyone had any recommendations for setup in this instance or if I'm doing it right as is.

Thanks,

Gary

Top
Sun, 06/03/2012 - 21:27
mikew
Offline
Joined: 03/14/2011
Groups:

In order to get the best performance you just need to make sure that your working set fits into memory. This means if during peak hours your server is using 10GB of data you need to make sure you have 10GB of memory. If you have 20GB of data in use and only 10GB of memory you will take a performance hit.

Adding more nodes is not likely to add any extra speed in your case. If your working set is in memory then a single node can sustain over 100k ops/sec and give you sub-millisecond responses. I would recommend adding a second node so that your data is replicated though.

Top