From: =?iso-8859-1?Q?Michael_Gr=F8nager?= <gronager@ceptacle.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Date: Thu, 15 Dec 2011 18:18:09 +0100
Message-Id: <EC9F1E66-F4B7-4FCE-AF98-F1BAF43B39D9@ceptacle.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: [Bitcoin-development] CDataStream
Precedence: list

OK, I admit that this is *really* of little importance...=20

But could someone with commit rights please update the CDataStream test =
table in the code. The arguments for the custom stream are just way off =
(stringstream wins by factor 10-20!). On OS X (g++) I get:

Further, if you get(got) bad stringstream numbers on e.g. windows =
(dikumware had some issues several years ago) you can improve just by =
changing the default allocation chunk size. So... speed is not a reason =
for reimplementing stringstream. (And perhaps this can motivate someone =
to revert bitcoin to stringstream ;-)

Cheers,

Michael

PS: Could be fun to see the output on other OS'es !

serialize.h (with TESTCDATASTREAM defined, =
i686-apple-darwin11-llvm-g++-4.2 (GCC) 4.2.1 (Based on Apple Inc. build =
5658) (LLVM build 2336.1.00)):

CDataStream:
n=3D1000       0 seconds
n=3D2000       0 seconds
n=3D4000       0 seconds
n=3D8000       0 seconds
n=3D16000      0 seconds
n=3D32000      0 seconds
n=3D64000      1 seconds
n=3D128000     1 seconds
n=3D256000     2 seconds
n=3D512000     4 seconds
n=3D1024000    8 seconds
n=3D2048000    17 seconds
n=3D4096000    40 seconds
stringstream:
n=3D1000       0 seconds
n=3D2000       0 seconds
n=3D4000       0 seconds
n=3D8000       0 seconds
n=3D16000      0 seconds
n=3D32000      0 seconds
n=3D64000      0 seconds
n=3D128000     0 seconds
n=3D256000     0 seconds
n=3D512000     0 seconds
n=3D1024000    0 seconds
n=3D2048000    1 seconds
n=3D4096000    2 seconds