Will do!

On Thu, Jan 12, 2017 at 4:12 PM Garren Smith <[email protected]> wrote:

> Brilliant. We always appreciate feedback on Mango so please let us know how
> it goes.
>
> Cheers
> Garren
>
> On Thu, Jan 12, 2017 at 5:35 PM, Dan Ballance <[email protected]>
> wrote:
>
> > Hi Garren,
> >
> > Thanks ever so much for your response. That makes a lot of sense. 100K
> > results is still a pretty usable limit and means we can take advantage of
> > mango query's flexibility in the majority of scenarios we'll encounter.
> >
> > thanks again,
> >
> > Dan
> >
> > On Thu, Jan 12, 2017 at 3:09 PM Garren Smith <[email protected]> wrote:
> >
> > > Hi Dan,
> > >
> > > Mango Query is using Map Reduce underneath. At this stage its best to
> use
> > > mango query where you will get small data sets returned.
> > > Depending on your application using skip should be fine up to around
> 100
> > > 000 docs or do. So if you are paginating for a user it should work
> fine.
> > > But its best to test for your use case.
> > >
> > > Cheers
> > > Garren
> > >
> > > On Wed, Jan 11, 2017 at 4:33 PM, Dan Ballance <[email protected]
> >
> > > wrote:
> > >
> > > > Hi folks,
> > > >
> > > > Is there anybody here that can talk about the performance
> > characteristics
> > > > of Mango query? In particular I'm thinking about pagination over
> large
> > > data
> > > > sets. The mango query _find API doesn't seem to have startkey, only
> > > > skip. I'm not clear if that means the performance of skip is fine
> with
> > a
> > > > mango query - or whether mango query should only be used for small
> data
> > > > sets?
> > > >
> > > > Is anyone able to offer some guidance here please? For the time
> being I
> > > am
> > > > using skip, but I'm not sure if this is a good idea.
> > > >
> > > > FYI I have also asked this question on Stack Overflow:
> > > >
> > > > http://stackoverflow.com/questions/41587884/is-startkey-
> > > > pagination-required-for-mango-queries-in-couchdb-2-0
> > > >
> > > > sincerely,
> > > >
> > > > Dan Ballance.
> > > >
> > >
> >
>

Reply via email to