Re: LevelDB driver

On Mon, Jul 4, 2011 at 10:33 AM, Jonathan Langevin wrote: > Thanks Justin for the helpful response :-) Happy to help. > Can you define what you would consider "huge" regarding # keys? A bit depends on the details (such as key size) but generally the tipping point is somewhere near ten million

Re: LevelDB driver

Thanks Justin for the helpful response :-) * Can you define what you would consider "huge" regarding # keys? Jonathan Langevin Systems Administrator Loom Inc. Wilmington, NC: (910) 241-0433 - jlange...@loomlearning.com - www.loomlearning.com - Skype: intel352 * On

Re: LevelDB driver

Hi, Jonathan. On Mon, Jul 4, 2011 at 9:42 AM, Jonathan Langevin wrote: > I've seen users show concern of Bitcask's space usage overhead. How does that > compare against LevelDB? Bitcask doesn't have much in the way of disk space "overhead" unless you mean that the space used by deleted or overw

Re: LevelDB driver

I've seen users show concern of Bitcask's space usage overhead. How does that compare against LevelDB? Would LevelDB be a good solution for log data? If using a Level backend, what advantages do we lose of Bitcask? ls replication & availability an issue at all? * Jo