Re: [HACKERS] WAL: O_DIRECT and multipage-writer

2005-03-23 Thread Mark Wong
On Wed, Mar 23, 2005 at 01:55:46PM +0900, ITAGAKI Takahiro wrote: > Hi, Mark. > > Mark Wong <[EMAIL PROTECTED]> wrote: > > > In light of this thread, have you compared the performance on > > Linux-2.4? > > No, but I'm just testing my patch on Linux-2.4 with a middle-range server. > I will report

Re: [HACKERS] WAL: O_DIRECT and multipage-writer

2005-03-22 Thread ITAGAKI Takahiro
Hi, Mark. Mark Wong <[EMAIL PROTECTED]> wrote: > In light of this thread, have you compared the performance on > Linux-2.4? No, but I'm just testing my patch on Linux-2.4 with a middle-range server. I will report the results sometime soon. By the way, I found the debug option (XLOG_MULTIPAGE_W

Re: [HACKERS] WAL: O_DIRECT and multipage-writer

2005-03-22 Thread Mark Wong
On Tue, Jan 25, 2005 at 06:06:23PM +0900, ITAGAKI Takahiro wrote: > Environment: > OS : Linux kernel 2.6.9 > CPU: Pentium 4 3GHz > disk : ATA 5400rpm (Data and WAL are placed on same partition.) > memory : 1GB > config : shared_buffers=1, wal_buffers=256, >XLOG_S

Re: [HACKERS] WAL: O_DIRECT and multipage-writer

2005-02-14 Thread Bruce Momjian
This thread has been saved for the 8.1 release: http://momjian.postgresql.org/cgi-bin/pgpatches2 --- ITAGAKI Takahiro wrote: > Hello, all. > > I think that there is room for improvement in WAL. > Here is a patch f

Re: [HACKERS] WAL: O_DIRECT and multipage-writer

2005-01-27 Thread Mark Wong
Hi everyone, I gave this a try with DBT-2, but got a core dump on our ia64 system. I hope this isn't a random thing, like I ran into previously. Maybe I'll try again, but postgres dumped core. Binary and core here: http://developer.osdl.org/markw/pgsql/core/2morefiles.tar.bz2 #0 Functi

Re: [HACKERS] WAL: O_DIRECT and multipage-writer

2005-01-26 Thread ITAGAKI Takahiro
Tom Lane <[EMAIL PROTECTED]> writes: > What does XLOG_EXTRA_BUFFERS accomplish? It is because the buffer passed to direct-io must be aligned to the same size of filesystem page, typically 4KB. Buffers allocated with ShmemInitStruct are not necessarily aligned, so we need to allocate extra buffer