Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 356736DF4 for ; Wed, 6 Jul 2011 04:46:07 +0000 (UTC) Received: (qmail 83658 invoked by uid 500); 6 Jul 2011 04:46:05 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 82975 invoked by uid 500); 6 Jul 2011 04:45:57 -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 82918 invoked by uid 99); 6 Jul 2011 04:45:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jul 2011 04:45:53 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of maxosmail@gmail.com designates 209.85.220.180 as permitted sender) Received: from [209.85.220.180] (HELO mail-vx0-f180.google.com) (209.85.220.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Jul 2011 04:45:48 +0000 Received: by vxd7 with SMTP id 7so6875635vxd.11 for ; Tue, 05 Jul 2011 21:45:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=vJGS5hx1c04R0qLJAfGPkh3x85nAsmjjsSrIo42d4XQ=; b=iw9Er+5xasFi15NNkj+apw5H83jOGvWOzZZUgcD+oscZVrl/cZ2Z3h9HprBrzi6we4 UhzQSMxWTicOEs+MiOl9QRhC/lVujtWZXH70FvXmQNupJ8TAyN6vEv2Gi4PdGwVJCZAh UXl9Uw3IRg+gNkU5hh8trk7p4O/SHVgxQ4Gt4= Received: by 10.52.177.166 with SMTP id cr6mr7351199vdc.151.1309927527120; Tue, 05 Jul 2011 21:45:27 -0700 (PDT) MIME-Version: 1.0 Sender: maxosmail@gmail.com Received: by 10.52.114.170 with HTTP; Tue, 5 Jul 2011 21:45:07 -0700 (PDT) In-Reply-To: <4E13DED5.1020100@gmail.com> References: <4E13A5A0.8060103@gmail.com> <4E13DED5.1020100@gmail.com> From: Max Ogden Date: Tue, 5 Jul 2011 21:45:07 -0700 X-Google-Sender-Auth: qODFggKkPWnVvq04o1B2NusCp58 Message-ID: Subject: Re: few doubts To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=20cf3071ccaaef7d2e04a75f444d --20cf3071ccaaef7d2e04a75f444d Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Jason Smith (github/iriscouch) wrote a utility called the CouchDB Heater cause it keeps your views warm. If you ask nicely he will probably put the source code on the internets On Tue, Jul 5, 2011 at 9:04 PM, Patrick Barnes wrote: > Why not create and publish an equivalent javascript version then? It seem= s > like it would be a valuable addition to the couchdb suite. > > (FWIW, php can just be installed on its own, and it will run command-line > scripts just fine) > > > On 6/07/2011 1:59 PM, Mark Hahn wrote: > >> Any way to run PHP with Node without installing lampp? I guess I >> could just steal the logic. >> >> On Tue, Jul 5, 2011 at 5:00 PM, Patrick Barnes wrote= : >> >>> I have written a PHP script for my application to do this seamless >>> update: >>> https://gist.github.com/**1066246 >>> I find it very useful! My rebuild time is about 30 minutes, so if it >>> blocked >>> I'd have users screaming at me in short order. >>> >>> One or two aspects of the script are app-specific, but it should be >>> fairly >>> easy to understand and to tailor for your own use. >>> >>> -Patrick >>> >>> >>> >>> On 6/07/2011 7:44 AM, Mark Hahn wrote: >>> >>>> >>>> Cool. That is much easier. Still a bit of a pain. It would be nice = if >>>> it >>>> did this automatically on every view change. >>>> >>>> On Tue, Jul 5, 2011 at 2:31 PM, Sean Copenhaver >>>> **wrote: >>>> >>>> CouchDB actually relates a design document to it's views by I believe= a >>>>> hash >>>>> of the design document contents (not the id). The wiki actually has a >>>>> how >>>>> to >>>>> for deploy view changes in a live environment: >>>>> >>>>> >>>>> >>>>> https://wiki.apache.org/**couchdb/How_to_deploy_view_** >>>>> changes_in_a_live_environment >>>>> >>>>> On Tue, Jul 5, 2011 at 5:17 PM, Mark Hahn >>>>> wrote: >>>>> >>>>> With CouchDB, all you have to do is to create your view within a >>>>>>> design >>>>>>> >>>>>> >>>>>> document and it will on its own build the actual "indices" (the view= s) >>>>>> >>>>> >>>>> the >>>>> >>>>>> >>>>>> very first time that those views are actually being used. The next >>>>>> time >>>>>> that those views are used, then only newly created and/or updated do= cs >>>>>> >>>>> >>>>> need >>>>> >>>>>> >>>>>> to be indexed. >>>>>> >>>>>> Actually, if you change a view in the design doc it rebuilds ALL vie= ws >>>>>> in >>>>>> that doc from scratch for ALL documents. This was a surprise to me >>>>>> the >>>>>> first time it happened because my entire application froze up for >>>>>> several >>>>>> minutes. I can imagine it happening for an hour with a giant db. T= he >>>>>> >>>>> >>>>> only >>>>> >>>>>> >>>>>> way I can figure out how to get around this problem is to create a >>>>>> second >>>>>> db, sync the main db to the second, rebuild the views on the second >>>>>> and >>>>>> then >>>>>> overwrite the main db file with the second db file. Kind of a pain. >>>>>> >>>>>> On Tue, Jul 5, 2011 at 11:17 AM, Randall Leeds< >>>>>> randall.leeds@gmail.com >>>>>> >>>>>>> >>>>>>> wrote: >>>>>>> >>>>>> >>>>>> I like everything you've said in these last three messages which we= re >>>>>>> meant to be one. :) >>>>>>> You should make it a blog post. For real. >>>>>>> >>>>>>> On Tue, Jul 5, 2011 at 00:32, Zdravko Gligic >>>>>>> >>>>>> >>>>> wrote: >>>>> >>>>>> >>>>>>>> oh, i hate gmail, as it seems to react to certain key combinations >>>>>>>> >>>>>>> >>>>> ... >>>>> >>>>>> >>>>>>>> Focus - It seems that CouchDB has been purposely designed with >>>>>>>> >>>>>>> >>>>> "single >>>>> >>>>>> >>>>>>>> mindedness in mind". The approach seems to be that it can be most >>>>>>>> efficient if its various functions and its various tasks do small >>>>>>>> amounts of work in the most efficient way possible. So, it would >>>>>>>> >>>>>>> >>>>> seem >>>>> >>>>>> >>>>>>>> that writes keep on writing to the end of file, instead of flippin= g >>>>>>>> through it and trying to over-write and update in place existing >>>>>>>> >>>>>>> >>>>> docs. >>>>> >>>>>> >>>>>>>> Again, in order to be as efficient as it can be with those writes= , >>>>>>>> >>>>>>> >>>>> it >>>>> >>>>>> >>>>>>>> foregoes updating the views (the same way that an RDBMS would upda= te >>>>>>>> all of the related indices as part of its record update) and leave= s >>>>>>>> >>>>>>> >>>>> it >>>>> >>>>>> >>>>>>>> for another process which will concentrate on doing just that. So= , >>>>>>>> >>>>>>> >>>>> it >>>>> >>>>>> >>>>>>>> seems that "context switching" or not having to do much of such >>>>>>>> switching is where it gets lots of it processing efficiency. >>>>>>>> >>>>>>>> Again, I am most anxious to see how my noob understandings check o= ut >>>>>>>> with technical realities. ;) >>>>>>>> >>>>>>>> HTH, >>>>>>>> teslan >>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> =E2=80=9CThe limits of language are the limits of one's world. =E2=80= =9C -Ludwig von >>>>> Wittgenstein >>>>> >>>>> >>>> >>> >> --20cf3071ccaaef7d2e04a75f444d--