You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Bernhard Schauer <be...@openforce.com> on 2012/07/05 07:21:08 UTC
Cached temporary views
Hello,
I want to measure the performance of index creation (building up a new
view) on my server.
I'm interested in the effects of adding an extra CPU.
My idea was to create a temporary view and and measure the response time
on the client.
But temporary views seem to be cached. When I request the same temporary
view twice, the second request is much faster.
Is there a way to prevent couchdb from caching temporary views? Or can I
clear the cache somehow?
Thanks Bernhard
--
openForce Information Technology GesmbH
Dresdner Str. 108 / 11
1200 Wien
Geschaeftsfuehrung: Otto Meinhart, Gerhard Hipfinger
Firmenbuch: Handelsgericht Wien, Sitz Wien, FN 218366b
http://openforce.com/
Re: Cached temporary views
Posted by Bernhard Schauer <be...@openforce.com>.
thanks Simon. Then I'll go with adding a bunch of documents
Am 2012-07-05 15:17, schrieb Simon Metson:
> Hi,
>> e.g. upload the same view code to multiple design documents
>>
>>
> Should have been
>
> e.g. upload the same view code to multiple databases
>
> The view files are named as a hash of the view function, so if you have duplicate code you just serve the same file to both.
>
> Sorry about that, thanks Bob for nudging me.
> Simon
>
>
> On Thursday, 5 July 2012 at 11:25, Simon Metson wrote:
>
>> Hi,
>> I think you'd be better off making fresh views (e.g. upload the same view code to multiple design documents). The caching is a good thing (it saves you time and cpu!), I don't think it can be turned off. It's also not a realistic test to have it disabled, you're not going to run like that in production. You could rm the view file between tests, I suppose.
>>
>> A better test might be to have a view defined, insert N documents hit the view and time the response, add another N docs, time the view, repeat etc. That way you can work out how quickly your view builds for a given set of docs. There are some tools to generate fake data, which is handy for this kind of test.
>> Cheers
>> Simon
>>
>> On Thursday, 5 July 2012 at 06:21, Bernhard Schauer wrote:
>>
>>> Hello,
>>>
>>> I want to measure the performance of index creation (building up a new
>>> view) on my server.
>>> I'm interested in the effects of adding an extra CPU.
>>>
>>> My idea was to create a temporary view and and measure the response time
>>> on the client.
>>> But temporary views seem to be cached. When I request the same temporary
>>> view twice, the second request is much faster.
>>>
>>> Is there a way to prevent couchdb from caching temporary views? Or can I
>>> clear the cache somehow?
>>>
>>> Thanks Bernhard
>>>
>>> --
>>> openForce Information Technology GesmbH
>>> Dresdner Str. 108 / 11
>>> 1200 Wien
>>>
>>> Geschaeftsfuehrung: Otto Meinhart, Gerhard Hipfinger
>>> Firmenbuch: Handelsgericht Wien, Sitz Wien, FN 218366b
>>>
>>> http://openforce.com/
>
--
openForce Information Technology GesmbH
Dresdner Str. 108 / 11
1200 Wien
Geschaeftsfuehrung: Otto Meinhart, Gerhard Hipfinger
Firmenbuch: Handelsgericht Wien, Sitz Wien, FN 218366b
http://openforce.com/
Re: Cached temporary views
Posted by Simon Metson <si...@cloudant.com>.
Hi,
> e.g. upload the same view code to multiple design documents
>
>
Should have been
e.g. upload the same view code to multiple databases
The view files are named as a hash of the view function, so if you have duplicate code you just serve the same file to both.
Sorry about that, thanks Bob for nudging me.
Simon
On Thursday, 5 July 2012 at 11:25, Simon Metson wrote:
> Hi,
> I think you'd be better off making fresh views (e.g. upload the same view code to multiple design documents). The caching is a good thing (it saves you time and cpu!), I don't think it can be turned off. It's also not a realistic test to have it disabled, you're not going to run like that in production. You could rm the view file between tests, I suppose.
>
> A better test might be to have a view defined, insert N documents hit the view and time the response, add another N docs, time the view, repeat etc. That way you can work out how quickly your view builds for a given set of docs. There are some tools to generate fake data, which is handy for this kind of test.
> Cheers
> Simon
>
> On Thursday, 5 July 2012 at 06:21, Bernhard Schauer wrote:
>
> > Hello,
> >
> > I want to measure the performance of index creation (building up a new
> > view) on my server.
> > I'm interested in the effects of adding an extra CPU.
> >
> > My idea was to create a temporary view and and measure the response time
> > on the client.
> > But temporary views seem to be cached. When I request the same temporary
> > view twice, the second request is much faster.
> >
> > Is there a way to prevent couchdb from caching temporary views? Or can I
> > clear the cache somehow?
> >
> > Thanks Bernhard
> >
> > --
> > openForce Information Technology GesmbH
> > Dresdner Str. 108 / 11
> > 1200 Wien
> >
> > Geschaeftsfuehrung: Otto Meinhart, Gerhard Hipfinger
> > Firmenbuch: Handelsgericht Wien, Sitz Wien, FN 218366b
> >
> > http://openforce.com/
>
Re: Cached temporary views
Posted by Simon Metson <si...@cloudant.com>.
Hi,
I think you'd be better off making fresh views (e.g. upload the same view code to multiple design documents). The caching is a good thing (it saves you time and cpu!), I don't think it can be turned off. It's also not a realistic test to have it disabled, you're not going to run like that in production. You could rm the view file between tests, I suppose.
A better test might be to have a view defined, insert N documents hit the view and time the response, add another N docs, time the view, repeat etc. That way you can work out how quickly your view builds for a given set of docs. There are some tools to generate fake data, which is handy for this kind of test.
Cheers
Simon
On Thursday, 5 July 2012 at 06:21, Bernhard Schauer wrote:
> Hello,
>
> I want to measure the performance of index creation (building up a new
> view) on my server.
> I'm interested in the effects of adding an extra CPU.
>
> My idea was to create a temporary view and and measure the response time
> on the client.
> But temporary views seem to be cached. When I request the same temporary
> view twice, the second request is much faster.
>
> Is there a way to prevent couchdb from caching temporary views? Or can I
> clear the cache somehow?
>
> Thanks Bernhard
>
> --
> openForce Information Technology GesmbH
> Dresdner Str. 108 / 11
> 1200 Wien
>
> Geschaeftsfuehrung: Otto Meinhart, Gerhard Hipfinger
> Firmenbuch: Handelsgericht Wien, Sitz Wien, FN 218366b
>
> http://openforce.com/