Path: csiph.com!x330-a1.tempe.blueboxinc.net!usenet.pasdenom.info!weretis.net!feeder4.news.weretis.net!newsfeed.utanet.at!newscore.univie.ac.at!newsfeed01.chello.at!newsfeed02.chello.at!news.hispeed.ch.POSTED!not-for-mail
Content-Type: text/plain; charset=iso-8859-15; format=flowed; delsp=yes
Newsgroups: comp.lang.c++
Subject: Re: STL vector / Heap fragmentation
References: <op.v4z6q8m5vc68pg@hp2011.workgroup> <4ec2cbd5$0$6638$9b4e6d93@newsspool2.arcor-online.net> <Mb2dneNfZZSJS1_TnZ2dnUVZ8iednZ2d@giganews.com> <4ec2dda9$0$6635$9b4e6d93@newsspool2.arcor-online.net> <b5SdnddrZNbBfF_TnZ2dnUVZ8nOdnZ2d@giganews.com> <op.v404l3vavc68pg@hp2011.workgroup> <9c5c6efa-78d6-478e-8591-59334000a6a7@o17g2000yqa.googlegroups.com>
Date: Wed, 16 Nov 2011 10:58:51 +0100
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Peter Liedermann" <peter09876@hispeed.ch>
Message-ID: <op.v4090dxovc68pg@hp2011.workgroup>
User-Agent: Opera Mail/11.52 (Win32)
X-Complaints-To: abuse@hispeed.ch
Organization: hispeed.ch
Lines: 15
NNTP-Posting-Host: 80.219.145.247 (80.219.145.247)
NNTP-Posting-Date: Wed, 16 Nov 2011 11:00:55 +0100
X-Trace: 27f374ec389d7f57e345217414
Xref: x330-a1.tempe.blueboxinc.net comp.lang.c++:11507

On Wed, 16 Nov 2011 09:39:29 +0100, Goran <goran.pusic@gmail.com> wrote:


> It's perhaps worth adding that sorting the vector<Jumbo> in itself
> doesn't affect heap fragmentation, as sorting should be in-place.

also if the Jumbo* instances are of varying length?


> Rather, any allocations that Jumbo copying makes affect it. It Jumbo
> is big, but of small pieces, then it's likely you won't be affected.

Wouldn't Jumbo big and of small pieces make fragmentation worse?

Peter