![]() | |||||||||||
Messages in this thread |
> > These are nice-looking numbers, but one wonders. If optimising readahead > > makes this much difference to postgresql performance then postgresql should > > be doing the readahead itself, rather than relying upon the kernel's > > ability to guess what the application will be doing in the future. Because > > surely the database can do a better job of that than the kernel. > With that argument we should remove all readahead from the kernel? > Because it's already trying to guess what the application will do. > I suspect it's better to have good readahead code in the kernel > than in a zillion application. Maybe a pluggable read-ahead system could be implemented. Folkert van Heusden -- Ever wonder what is out there? Any alien races? Then please support the seti@home project: setiathome.ssl.berkeley.edu ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2006-05-27 01:57 [from the cache] ©2003-2008 | |||||||||||