Re: odd postgresql performance (excessive lseek)

From: Greg Smith <greg(at)2ndquadrant(dot)com>
To: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: odd postgresql performance (excessive lseek)
Date: 2010-10-19 16:28:29
Message-ID: 4CBDC72D.3080301@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jon Nelson wrote:
> That's a little harsh (it's not untrue, though).
>

Welcome to pgsql-performance! You can get a right answer, or a nice
answer, but given the personalities involved it's hard to get both at
the same time. With this crowd, you need to be careful stating
something you were speculating about as if you were certain of it, and
to be certain here usually means "I read the source code". I recommend
writing theories as a question ("would X have sped this up?") rather
than a statement ("X will speed this up") if you want to see gentler
answers.

> Has any work been done on making use of shared memory for file stats
> or using fallocate (or posix_fallocate) to allocate files in larger
> chunks?
>

Just plain old pre-allocating in larger chunks turns out to work well.
Am hoping to get that into an official patch eventually.

--
Greg Smith, 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services and Support www.2ndQuadrant.us
Author, "PostgreSQL 9.0 High Performance" Pre-ordering at:
https://www.packtpub.com/postgresql-9-0-high-performance/book

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Merlin Moncure 2010-10-19 17:41:04 Re: odd postgresql performance (excessive lseek)
Previous Message Jon Nelson 2010-10-19 15:27:48 Re: odd postgresql performance (excessive lseek)