Hi Ian,
thanks a lot for the answer. Yes this are all important points to consider.
Have you a suggestion what's could be better. Have a 'small'
ring_creation_size and servers with lets say 20 TB / server or a higher
ring_creation_size and more servers with only 4 TB / server.
Best regards
Sebas
Hi Ian,
thanks for your reply. First, thank's a lot for explain the read process
in riak. It helps a lot.
For the benchmarks i use 4 Server:
CPU: 1x Intel(R) Xeon(R) CPU X5670 @ 2.93GHz
RAM: 16 GB
NET: 1 GBit interface
I believe that a cluster can perform over 500 reques
On Tuesday, January 24, 2012 at 5:21 AM, Sebastian Gerlach wrote:
> Some other points in my considerations are the time required for a
> reorganization after a new node are added to the cluster or a node has
> been replaced.
>
>
Sebastian,
Sorry I missed this part of your question.
The time
Sebastian,
With all requests, Riak will attempt to read or write to all replicas
regardless of the specified r or w value. The r and w values affect how many
reads from or writes to partitions must be completed before the operation is
considered successful.
As a result, the get (read) and put
Dear Riak-Users,
we consider to save a large amount (5000) of binary Data (Images) in
a riak cluster. Each image has a size of 648 KB. We want to store 3
copy's of each image.
In this case i need to store 5000 * 648 KB * 3 = 90.5 TB Data. This
calculation didn't include any overhead for
