Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of jens@mooseyard.com designates
 208.97.132.145 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=mooseyard.com; h=references
	:in-reply-to:mime-version:content-transfer-encoding:content-type
	:message-id:cc:from:subject:date:to; q=dns; s=mooseyard.com; b=f
	k7QNCLznajdAGxJ/Ea4SNdYxo0TSucptEm5XNbQKN4VtCvud38jQihJ2ZzD+dAbR
	zxUy7sn8KQXmTsHHUWiZkjLwFgIztcpWZSwBasgIRSMenZxYlc2ZT1d7WcxrX4lB
	xyAYP11A23syRg87CbH3qKkmLwq4VmzHqE00r1lRp8=
References: 
 <CAFvzuQEHss49Cg0WzcoHv4c=gEJ+4s-GXC0xuMRbZdQyvqQd5g@mail.gmail.com>
In-Reply-To: 
 <CAFvzuQEHss49Cg0WzcoHv4c=gEJ+4s-GXC0xuMRbZdQyvqQd5g@mail.gmail.com>
Mime-Version: 1.0 (iPad Mail 8J2)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii
Message-Id: <C46D8624-3F7A-4223-A888-ECC3B2A01018@mooseyard.com>
Cc: "user@couchdb.apache.org" <user@couchdb.apache.org>
From: Jens Alfke <jens@mooseyard.com>
Subject: Re: few doubts
Date: Sun, 3 Jul 2011 20:26:46 -0700
To: "user@couchdb.apache.org" <user@couchdb.apache.org>


On Jul 3, 2011, at 8:11 PM, Matthew John <tmatthewjohn1988@gmail.com> wrote:=


> 1) I am familiar with MySql systems. In one of the applications I ve made,=

> whenever the server gets restarted I used to perform a warm up (similar to=

> Select * from *) inorder to populate the cache. And this used to take almo=
st
> like half an hour. How does it happen in CuuchDB and how long might it tak=
e
> for the "warm up"

That sounds like it would depend totally on the size of the database, and th=
e server's disk speed and amount of RAM. (It seems like a strange thing to d=
o anyway; shoving every row through the cache is going to leave it in a fair=
ly random state that won't reflect how much different rows actually get used=
.)

> 2) I understand that all the MR queries (views) to be used in the system h=
as
> to be coded in the Design document. Does that mean a super-set of all
> possible queries which we might use in the System has to be coded in the
> Design doc? Can this be added on the fly (dynamic)

Sure; design docs are just documents [rows] and can be updated at any time.

But in practice, most SQL based apps also have a fixed set of hardcoded quer=
ies that they plug parameters into at runtime, so this isn't very different.=


--Jens=