Are you trying to find a document in a database of 90k by reading _changes with a filter? If so, that is not the way to look up a document. Build a view and query by key.
Reading 90,000 documents will take time, regardless of how many you don't send over the wire. B. On 14 March 2013 12:11, Kevin R. Coombes <[email protected]> wrote: > Have you compacted both the database and the views? > > I ran into an issue where even paging through the results of a view always > slowed down substantially when I got to about document number 10000. After > compacting the view, the problem went away. > > Kevin > > > On 3/14/2013 9:00 AM, Arne Fischer wrote: >> >> We are using CouchDB as a Database in a Mobile context. Because of this >> performance and data size is a problem and very important to us. >> We tried writing a filter in erlang within a design element, but sadly we >> didn't notice a upgrade in speed. It takes us about 3 minutes to find >> documents within a database of 90k elements. >> These filters will later be used to replicate the database to a mobile >> device. >> Code samples are in this >> http://stackoverflow.com/questions/15388488/very-slow-filters-with-couchdb-even-with-erlang >> Stack overflow post. >> How is it possible to increase filter speed? >> Is it a mistake to write erlang filters within the _design/ documents? If >> yes where do you put the filter? >> We would really like to use CouchDB more and this is hindering us right >> now. >> >> kind regards, >> Arne Fischer
