Re: [HACKERS] memory allocation and powers of two

2003-09-14 Thread David Schultz
On Sat, Sep 13, 2003, Tom Lane wrote: > David Schultz <[EMAIL PROTECTED]> writes: > > While looking into a block size mismatch problem between > > Postgresql and FreeBSD's FFS, I noticed that postgresql is making > > some rather odd-sized requests to malloc(3): 0x

Re: [HACKERS] Bumping block size to 16K on FreeBSD...

2003-08-29 Thread David Schultz
On Thu, Aug 28, 2003, Tom Lane wrote: > Sean Chittenden <[EMAIL PROTECTED]> writes: > > Are there any objections > > to me increasing the block size for FreeBSD installations to 16K for > > the upcoming 7.4 release? > > I'm a little uncomfortable with introducing a cross-platform variation > in th

Re: [HACKERS] Bumping block size to 16K on FreeBSD...

2003-08-29 Thread David Schultz
On Thu, Aug 28, 2003, scott.marlowe wrote: > On Thu, 28 Aug 2003, Marc G. Fournier wrote: > > On Thu, 28 Aug 2003, Thomas Swan wrote: > > > > > Has anyone looked at changing the default block size across the board > > > and what the performance improvements/penalties might be? Hardware has > > >

[HACKERS] memory allocation and powers of two

2003-08-28 Thread David Schultz
While looking into a block size mismatch problem between Postgresql and FreeBSD's FFS, I noticed that postgresql is making some rather odd-sized requests to malloc(3): 0x2034, 0x2020, 0x4018, 0x8018, etc. Most malloc(3) implementations round large allocations up to a multiple of a large power of 2