Re: Utilizing "direct writes" Re: File system performance and pg_xlog
От | Marko Kreen |
---|---|
Тема | Re: Utilizing "direct writes" Re: File system performance and pg_xlog |
Дата | |
Msg-id | 20010506123448.B20919@l-t.ee обсуждение исходный текст |
Ответ на | Utilizing "direct writes" Re: File system performance and pg_xlog (Alfred Perlstein <bright@wintelcom.net>) |
Ответы |
Re: Utilizing "direct writes" Re: File system performance and pg_xlog
|
Список | pgsql-hackers |
On Sat, May 05, 2001 at 07:01:35PM -0700, Alfred Perlstein wrote: > * Marko Kreen <marko@l-t.ee> [010505 17:39] wrote: > > * double-buffering and incompatibilities of avoiding that > > Depends on the OS, most Operating systems like FreeBSD and Solaris > offer character device access, this means that the OS will DMA > directly from the process's address space. Avoiding the double > copy is trivial except that one must align and size writes correctly, > generally on 512 byte boundries and in 512 byte increments. PostgreSQL must then also think about write ordering very hard, atm this OS business. > > * the speed difference will not be very big. Remeber: it _was_ > > big on OS'es and fs' in year 1990. Today's fs are lot of > > better and there should be a os/fs combo that is 95% perfect. > > Well, here's an idea, has anyone tried using the "direct write" > interface that some OS's offer? I doubt FreeBSD does, but I'm > positive that Solaris offers it as well as possibly IRIX. And how much it differs from using FAT? Thats the point I want to make. There should be already a fs that is 90% close that. -- marko
В списке pgsql-hackers по дате отправления: