On Mon, Sep 27, 2010 at 7:21 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
> Alvaro Herrera <alvhe...@commandprompt.com> writes: > > Excerpts from Gurjeet Singh's message of dom sep 26 22:15:59 -0400 2010: > >> Currently I am seeing a performance improvement of this script by only > about > >> 500 ms; say 11.8 seconds vs. 11.3 secs. But I remember distinctly that > >> yesterday I was able to see an improvement of 11% on the same virtual > >> machine, averaged on multiple runs; 42 sec vs 37 sec. It might be the > case > >> that the host OS or my Linux virtual machine were loaded at that time > and > >> the filesystem could not cache enough inodes. > > > Hmm. On my otherwise idle desktop machine, I can't measure a difference. > > Yeah, this seems like something that would have at best an > environment-specific effect. I'm not convinced that it couldn't make > things worse in some cases ... > I can't think of any obvious cases where this might hurt. I am unable to reproduce the 11% improvement, but I did see that dramatic change which prompted me for the patch. On the contrary, nothing so far suggests that it could hurt configure times. Regards, -- gurjeet.singh @ EnterpriseDB - The Enterprise Postgres Company http://www.EnterpriseDB.com singh.gurj...@{ gmail | yahoo }.com Twitter/Skype: singh_gurjeet Mail sent from my BlackLaptop device
