From user-return-10509-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Fri May 14 14:26:18 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 59663 invoked from network); 14 May 2010 14:26:18 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 14 May 2010 14:26:18 -0000 Received: (qmail 31193 invoked by uid 500); 14 May 2010 14:26:17 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 31147 invoked by uid 500); 14 May 2010 14:26:17 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 31139 invoked by uid 99); 14 May 2010 14:26:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 May 2010 14:26:17 +0000 X-ASF-Spam-Status: No, hits=3.3 required=10.0 tests=AWL,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of etil15@gmail.com designates 72.14.220.155 as permitted sender) Received: from [72.14.220.155] (HELO fg-out-1718.google.com) (72.14.220.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 May 2010 14:26:12 +0000 Received: by fg-out-1718.google.com with SMTP id 19so1447876fgg.5 for ; Fri, 14 May 2010 07:25:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=KhVZ6MK+VuLbfVcAGtBNmjP/PBhjddmSEjVpRB5vQNM=; b=CFQcPARCyLNYoj+EGRlhOmWDyL3yxbOVE/Ds20rXav41q9HgeH0BcvoJPdxM4/4OYq pfcydpw9PEqqb71/8jBXZ9DQAqA1SxoNW5q8/pgEa67KAnirv/ydMrfsk9eYOYoog0CJ +ug1g2jkhQS3eJlwi34dor1OMuVmnDp2BCpIk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=BAnZXBegHUyQU9VOnNnPJSlFFfhu5yMYTJ6c9XGZi4a5uC+rg+7bCV2ZdCzizlbHWu DquHLDXHHMl+Rn6ipPEgH5sjKaL1abIHGUW69sVuPcOm2FN102WIA1EMxe8DZowClWVI D4a35PJ+E2k+gJ1DqOMAOIt7ixydCzxwUitdg= MIME-Version: 1.0 Received: by 10.239.186.67 with SMTP id f3mr133905hbh.161.1273847150736; Fri, 14 May 2010 07:25:50 -0700 (PDT) Received: by 10.239.147.10 with HTTP; Fri, 14 May 2010 07:25:50 -0700 (PDT) In-Reply-To: <4BED5794.9000604@canonical.com> References: <6D88F5E9-1488-4EF3-A289-212AD2EE2E19@gmail.com> <4BED5794.9000604@canonical.com> Date: Fri, 14 May 2010 10:25:50 -0400 Message-ID: Subject: Re: Ars Technica finds DesktopCouch too laggy From: =?ISO-8859-1?Q?Manuel_de_la_Pe=F1a?= To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=001485f45090eaf7d704868ea613 --001485f45090eaf7d704868ea613 Content-Type: text/plain; charset=ISO-8859-1 On 14 May 2010 10:00, Eric Casteleijn wrote: > On 05/14/2010 08:43 AM, Wout Mertens wrote: > >> Hi group, >> >> I noticed with sadness the rather disappointing review of the DesktopCouch >> feature of Ubuntu at Ars Technica: >> >> >> http://arstechnica.com/open-source/reviews/2010/05/lucid-dream-ars-reviews-ubuntu-1004.ars/9 >> >> "The take-away point is that the amount of latency and CPU overhead that >> DesktopCouch introduces is just not conducive to building responsive desktop >> applications that run on a wide range of ordinary consumer hardware. In >> cases where the number of records is in the tens of thousands, it's more >> sensible to use SQLite and use DesktopCouch only for the parts that need to >> be synchronized." >> >> I wonder where the lag is introduced. DesktopCouch is, as I understand it, >> a Python API for storing and synchronizing user data like settings and chat >> logs, using CouchDB as the backend. >> > > That is correct: it's built on top of python-couchdb and is meant as a > library that allows users to synchronize structured data between their > machines and with a cloud, as well as allowing different applications to use > the same backend for the same kind of data. (So for instance storing > contacts from evolution in couch, and then having them accessible from any > other application that is interested in contacts.) > > > Is CouchDB too slow to use on a desktop system as a desktop database? >> > > By no means: I don't think any of the issues the gwibber developers have > run into are necessarily CouchDB problems. > > I think it's a mixture of a relatively young and fluid API (desktopcouch), > and some places where Gwibber could have optimized their usage of > desktopcouch/couchdb: right now it adds every incoming twitter/ > identi.ca/facebook message to the db one by one as it arrives, and > immediately requeries the view. If you follow a lot of people, or worse, > have a search stream open, this means the views are continually being > rebuilt, and you never get the speed benefit of a prebuilt view. > > It would help if incoming messages were added in bulk every x seconds, and > the views only queried once per minute or so. Personally, I've not had > issues with gwibber in quite a while. I think a lot of the issues in > desktopcouch (and some in Gwibber itself) have been found and ironed out. > > -- > eric casteleijn > https://code.launchpad.net/~thisfred > Canonical Ltd. > > Eric, I think the problem with gwibber is the fact that they are using desktopcouch and therefore CouchDB wrongly. The fact that messages are retrieved from the REST APIs of the social medias, transformed into gwibber understandable records, pushed into couchDB and later retrieved is probably THE problem. Every time they do that, the index of the views have to be updated. The whole process does not make bloody sense since they already have the data in memory, why would they push it in the db and read it afterwards??? Immediate push and pull from the db does not make any sense and it is a terrible algorithm. Knowing this you can decide whose "fault" it is.... To be honest, last time I jump off a building and broke my legs I blamed gravity, that heartless b****! it should stop working with I jump through the widow!! Mandel --001485f45090eaf7d704868ea613--