On Mon, May 23, 2011 at 10:53:29PM -0700, Anthony Molinaro wrote:
>
> On Mon, May 23, 2011 at 09:57:25PM -0600, David Smith wrote:
> > On Mon, May 23, 2011 at 9:39 PM, Anthony Molinaro
> > Thus, depending on
> > your merge triggers, more space can be used than is strictly necessary
> > to store t
On Mon, May 23, 2011 at 09:57:25PM -0600, David Smith wrote:
> On Mon, May 23, 2011 at 9:39 PM, Anthony Molinaro
> wrote:
> >
> > Bitcask-Capacity-Planning Cluster-Capacity-Planning Reality
> > RAM 34.9 GB 34.9 GB 70 GB
> > Disk 102 GB
On Mon, May 23, 2011 at 9:39 PM, Anthony Molinaro
wrote:
>
> Bitcask-Capacity-Planning Cluster-Capacity-Planning Reality
> RAM 34.9 GB 34.9 GB 70 GB
> Disk 102 GB 18.49 GB 341 GB
>
> So it looks to
Hi,
As I'm about to dramatically increase our riak investment by putting
lots more data into it. I figured I might try to run through the
capacity planning on the wiki.
Since my current setup is fairly small and manageable I decided to try
to see how accurately the capacity planning matches w
I'd like to add that riak-js 0.4.0rc3 has been released. I encourage
everybody to update from rc2 (critical bug fixed). We should be
hitting 0.4.0 final soon I hope!
https://github.com/frank06/riak-js
2011/5/23 Mark Phillips :
> Afternoon, Evening, Morning to All -
>
> For today's Recap: A con
Afternoon, Evening, Morning to All -
For today's Recap: A contribution to Luwak, a new Erlang Driver for
LevelDB, a podcast, talks, and more.
Enjoy.
Mark
Community Manager
Basho Technologies
wiki.basho.com
twitter.com/pharkmillups
Riak Recap for May 20 - 22
Greetings!
We are working with a riaksearch cluster that uses innostore as the primary
backend in tandem with merge_index that is required by search. From reading
the Basho wiki it looks like the following are the most important factors
affecting memory and performance:
• innostore
Jon,
Sounds like a neat project. Out of curiosity, what use cases do you imagine
for something like this?
In regards to riak_err you shouldn't have any troubles leaving it out. It's
purpose is to protect your VM from OOM issues related to error logging.
What's the warning you see?
-Ryan
On T