I too have had similar results/problems with Win32 & Hoard.  Some basic core testing/debugging is necessary before this is usable.

Gil Shapira <[EMAIL PROTECTED]> wrote:
Hi Guys,
 
I'm now working on an Image Processing project.
It runs on a Dual Xeon with hyper threading (4 logic processors).
I'v got 4 threads running and allocating about 1 GB of heap memory.
At the moment I'm using the default STL allocator, and as you can easily guess,
I suffer badly from a severe HEAP contention and CPU utilization does not go above 50 %. I tryed to call HOARD to the rescue, but encountered 2 problems:
 
1. The recommended installation (using winhoard.obj and winhoard.lib and /MD flag)
didnt work - I saw the hoard greeting text on my console, but new and delete were still taken from msvcrt.
 
2. When I used the second option (using libhoard.dll and the #pragma directive) The new and delete were taken from libhoard.dll as they should. Also CPU utilization went sky rocket 100% for a few seconds but my joy was short lived, as after few seconds the program crashed on a memory error (which does not occur when I run without HOARD)
 
Please advise,
 
Thanks,
 
Gil Shapira



YAHOO! GROUPS LINKS




Reply via email to