-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Smith:
> Flexibility is often expensive from a performance point of view. We
> regularly tell people here that they have to avoid using Linux's LVM for
> similar reasons--while it shouldn't be so slow, it is. Nothing you can
> do about it
River Tarnell wrote:
I'm now running a test using VxFS on SVM soft partitions to see if that
improves performance at all (but I'd much rather have the flexibility of
VxVM).
Flexibility is often expensive from a performance point of view. We
regularly tell people here that they have to avoid
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Greg Smith:
> What you should do is the following:
> postgresql.conf: wal_sync_method = open_datasync
> /sql/pg_xlog: 'noatime,cio,mincache=direct,convosync=direct
> That should work quite well.
Thanks. That reduced the import time to about 4hr
River Tarnell wrote:
My configuration was a VxFS filesystem mounted at /sql, 'noatime,cio',
and another mounted at /sql/pg_xlog,
'noatime,cio,mincache=direct,convosync=direct'. This forced direct I/O
for the WAL. Without VxVM, these filesystems were on plain disk slices.
With VxVM, I added the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm running Postgres 8.3.7 on Solaris 10 x64, using VxFS/VxVM 5.0 MP3.
I'm trying to determine the best storage configuration for my workload,
so I ran some tests of Postgres performance with various combinations of
VM and filesystem. What I noti
