Am 02.02.2006 um 13:23 schrieb Gustaf Neumann:
could not resist to try this on our p5 production system under
modest load
(64bit, linux, lpar with 25 processors, 8 dual-core with ibms
version of hyperthreading)
processor : 25
cpu : POWER5 (gr)
clock : 1904.448000MHz
revision : 2.3
Urgs!?? What is this for a monster-machine???
The timings what you get are what I expected on a multi-cpu box.
However all our single-cpu boxes are WAY slower with ckalloc
then with the regular malloc.
Do you happen to have a single-cpu box where you can try this out?
What I'm trying to understand is: is this pattern regular or not?
If yes, then the default tcl allocator used for threading builds
is sub-optimal for general builds and has to be runtime-dependent
(use it for multi-cpu boxes and not on single-cpu). But before I
go the tough way of getting this done in Tcl (I will definitely
experience fierce opposition from "works-for-me" people...) I'd
better collect some very hard ammunition...
If not, then something is wrong with ALL our single-box machines
which is very, very hard to believe...
Thanks,
Zoran
