u1db-discuss team mailing list archive

[Stuart Langridge <stuart.langridge@xxxxxxxxxxxxx>]

On Tue, 2011-11-15 at 13:20 -0500, Rodney Dawes wrote:
> On Tue, 2011-11-15 at 16:10 +0100, John Meinel wrote:
> > It would be nice to see real benchmarks before we decide it is
> > necessary. The DB is intended to be size limited (~20MB per db per
> > user). I have a dataset of 50k docs that totals 33MB in JSON, and
> > ~60MB in sqlite. I can deserialize all docs in <1s (I'll try to get a
> > more accurate timing) in python.
> 
> So, this is perhaps of a bit greater concern to me at the moment, than
> the issue of performance from serialize/deserialize of JSON. How is that
> size limit enforced, and how is it decided? I already have one use case
> where the DB would be 100MB (and probably larger), for a single
> application.

The size limit isn't enforced, per se. However, u1db basically assumes
that you won't store massive amounts of data in it, and this means that
it is reasonable to use algorithms or techniques or approaches which are
better for developers but do not cater as well to large amounts of data.

sil