You'll almost certainly want to use NTFS.
I suspect you'll want to set the NTFS Allocation Unit Size to 8192 or
some integer multiple of 8192, since I believe that is the pg page
size. XP format dialog will not allow you to set it above 4096, but
the command line format utility will. I do remember
2009/4/13 Ognjen Blagojevic :
> It is a student database for the college which is a client of ours. The size
> of the database should be around 1GB, half being binary data (images). Not
> more than 100 users at the time will be working with the application.
nice, if you want to store pics, I sugge
2009/4/13 Ognjen Blagojevic :
> Hi all,
>
> First, thank you all for your answers.
>
>
> Grzegorz Jaśkiewicz wrote:
>>
>> Give it a try, and please tell us what sort of application you want to
>> put on it.
>
> It is a student database for the college which is a client of ours. The size
> of the da
Jeff wrote:
> If you have a halfway OK raid controller, CFQ is useless. You can
fire
> up something such as pgbench or pgiosim, fire up an iostat and then
> watch your iops jump high when you flip to noop or deadline and
> plummet on cfq.
An interesting data point, but not, by itself, co
On Apr 10, 2009, at 2:47 AM, Albe Laurenz *EXTERN* wrote:
Grzegorz Jaskiewicz wrote:
acording to kernel folks, anticipatory scheduler is even better for
dbs.
Oh well, it probably means everyone has to test it on their own at
the
end of day.
In my test case, noop and deadline performed we
Hi all,
First, thank you all for your answers.
Grzegorz Jaśkiewicz wrote:
Give it a try, and please tell us what sort of application you want to
put on it.
It is a student database for the college which is a client of ours. The
size of the database should be around 1GB, half being binary da
--- On Mon, 13/4/09, Greg Smith wrote:
> From: Greg Smith
> Subject: Re: [PERFORM] 2.6.26 kernel and PostgreSQL
> To: "Glyn Astill"
> Cc: pgsql-performance@postgresql.org, "Kevin Grittner"
>
> Date: Monday, 13 April, 2009, 9:25 AM
> On Fri, 10 Apr 2009, Glyn Astill wrote:
>
> > So it was
On Fri, 10 Apr 2009, Glyn Astill wrote:
So it was only for connections over a unix socket, but wow; it's still
an ongoing issue.
The problem is actually with pgbench when running on a UNIX socket, not
with the PostgreSQL server itself. On my tests, the actual database
server itself seems to
