Hi Ashvinder, Replication speed is another important one, especially pull replications from a source database (Sync Gateway, CouchDB, etc.). Our use case for example relies on completing a pull of existing data before the app is really usable, so the faster that initial replication, the better.
Also, an issue related to query time is the time it takes to index views, from scratch or incrementally following a document update. Cheers, Matt Ashvinder Singh <[email protected]> wrote: > > >Hello All, > >I’m trying to come up with a criteria for doing benchmarking and >performance testing for Couchbase Lite iOS version and needed your >help. >Essentially trying to find the limits of the database and how does the >database behave in extreme edge cases. > >At present I have: > >- How many documents (small size ~ few MB) can be created in couchbase > lite > - How much time a query (exact queries, key ranges, etc) takes to > execute if we have large (10K) documents of small size > >So what other things I should add to the above list which are important >and >provide a good indication of limits/boundaries in the database? > >Thanks, > >Ashvinder -- You received this message because you are subscribed to the Google Groups "Couchbase Mobile" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mobile-couchbase/18318d77-fcae-4023-9308-fd8f8f37606e%40email.android.com. For more options, visit https://groups.google.com/groups/opt_out.
