garrensmith commented on issue #2129: _find performance issues URL: https://github.com/apache/couchdb/issues/2129#issuecomment-523840728 A _find shouldn’t be slower. It’s using map/reduce underneath. So it’s the same query engine. What does your _explain say? Is the index being used. You can also enable execution_stats to tell you how the find query went to get more insight. ________________________________ From: Nicu Spinu <[email protected]> Sent: Thursday, August 22, 2019 10:28 AM To: apache/couchdb Cc: Subscribed Subject: [apache/couchdb] _find performance issues (#2129) Description Although the docs advise to start using _find rather the regular db views, it looks like _find is at least 5x time slower than a regular view. Is that something expected? [image]<https://user-images.githubusercontent.com/35466661/63499019-afe7f700-c4cf-11e9-86cf-8580f101d45d.png> Steps to Reproduce USING NODEJS 1. Create a new index through .createIndex 2. Query the db through _find using fields to match the newly created index. 3. We queried for about 10k rows. It took about 3.8 seconds, while a regular view, for the same amout of data took 800ms. USING CURL The same as above. The execution took the same amount of time(3.8)s. Expected Behaviour The find execution should take at least the same amount of time, or less? Your Environment Nodejs under linux/mac-os. * CouchDB Version used: 2.3.1 * Browser name and version: * Operating System and version: Mac-os / Centos 7 Additional context — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub<https://github.com/apache/couchdb/issues/2129?email_source=notifications&email_token=AABL2AV4FCKUCPOLFN6YVCTQFZE3HA5CNFSM4IOSIVN2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HGW4IZQ>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AABL2AUEL2MGV4LS7XMZKVLQFZE3HANCNFSM4IOSIVNQ>.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
