[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Nel] Trouble with block memory allocator

From: Vianney Lecroart
Subject: RE: [Nel] Trouble with block memory allocator
Date: Tue, 25 Feb 2003 10:39:16 +0100

Hi 02,

Basically, I just create a .dsp .dsw, compiles your program (changing
printf by nlinfo ;) and here the result in release mode:

INF 1732: list_std  : 4690239 op/sec (4950000 op)
INF 1732: list_block: 6494437 op/sec (4950000 op)

I let the programmer of this class to reply more your email ;)

Vianney Lecroart
lead network programmer /
icq#: 6870415
homepage: GCS/E d- s+++: a- C+++$ UL++ P- L+++>+$ E+>- W++ N+ o?
w++$ O- M- V- PS- PE? Y PGP t 5? X+ R- tv++ b- DI D+ G e++ h-- r y?

> -----Original Message-----
> From: address@hidden [mailto:nel-all-
> address@hidden On Behalf Of Vincent Caron
> Sent: lundi 24 février 2003 20:56
> To: address@hidden
> Subject: [Nel] Trouble with block memory allocator
> Hello,
>    I'm having a hard time with the CSTLBlockAllocator and
> classes. I can't make them compile with gcc 3.2, VC.NET (with and
> without STLport). I can't make the default stub compile either. After
> wasting a wealth of time on unreadable compiler errors, I looked more
> closely at the code. I'm suspicious about the real gain about this
> and I would like to check some facts before going further into the STL
> nightmare. I'd be pleased to hear rationales and testimonies about the
> CSTLBlockAlllocator.
> I wrote a simple benchmark, but I can't run it since I did not manage
> compile the aforementioned classes. I'm curious about the results, if
> anybody with a compiling NeL tree could try it, that'd be cool :
> Unpack in code/nel/, it will create a test/memory/ path. VC.NET
> files included, it's a basic win32 console project statically linked
> with the NeL misc library. The result is the average number of
> alloc+dealloc couples executed per second, the greater the better.
> _______________________________________________
> Nel mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]