Mark,
We run it with the following configurations:
Extra Large Instance (Ec2):
15 GB memory
8 EC2 Compute Units (4 virtual cores with 2 EC2 Compute Units each)
1,690 GB instance storage
64-bit platform
I/O Performance: High
API name: m1.xlarge
Large (Ec2):
7.5 GB memory
4 EC2 Compute Units (2
On Wed, Apr 18, 2012 at 6:43 AM, vijayakumar wrote:
> Mark,
> Thanks for your help. I could say the number of keys would be in the
> range of millions and total number of buckets is 4.
>
>
What hardware are you running this on?
Mark
> Regards,
> Vijayakumar.
>
>
> On Tue, Apr 17, 2012 at
Mark,
Thanks for your help. I could say the number of keys would be in the
range of millions and total number of buckets is 4.
Regards,
Vijayakumar.
On Tue, Apr 17, 2012 at 9:15 PM, Mark Phillips wrote:
> Hi Vijayakumar,
>
>
> On Sat, Apr 14, 2012 at 2:57 AM, vijayakumar wrote:
>
>> Hi,
>>
Hi Vijayakumar,
On Sat, Apr 14, 2012 at 2:57 AM, vijayakumar wrote:
> Hi,
> As our application moves from one release to another, we need to alter
> the existing records in riak [Say changes like adding new field to the json
> with a default value]. What's the ideal way to handle such schema
Hi,
As our application moves from one release to another, we need to alter
the existing records in riak [Say changes like adding new field to the json
with a default value]. What's the ideal way to handle such schema changes
(if indexing is required for such fields). Is it possible to run a
mapre
