Michael Lesniak wrote:
Hello,
I've written a smaller example which reproduces the unusual behaviour.
Should I open a GHC-Ticket, too?
Hi,
I get these results:
$ time ./Temp +RTS -N1 -RTS 16
real0m16.010s
user0m10.869s
sys0m5.144s
$ time ./Temp +RTS -N2 -RTS 16
real
Hello,
getTime? I wonder if that number might be causing the problem; can you
replicate it with lower sys times?
That was it! Thanks Neil!
When I'm using some number crunching without getTime it works (with
more or less the expected speedup and usage of two cores) on my Ubuntu
9.10, too.
Out
Michael Lesniak wrote:
Hello,
getTime? I wonder if that number might be causing the problem; can you
replicate it with lower sys times?
That was it! Thanks Neil!
When I'm using some number crunching without getTime it works (with
more or less the expected speedup and usage of two
Michael Lesniak wrote:
Hello,
I'm currently developing some applications with explicit threading
using forkIO and have strange behaviour on my freshly installed Ubuntu
Karmic 9.10 (Kernel 2.6.31-14 SMP).
Setup:
Machine A: Quadcore, Ubuntu 9.04, Kernel 2.6.28-13 SMP
Machine B: AMD Opteron 875,
Hello,
I've written a smaller example which reproduces the unusual behaviour.
Should I open a GHC-Ticket, too?
-- A small working example which describes the problems (I have) with GHC
-- 6.10.4, Ubuntu Karmic 9.10, explicit threading and core usage.
--
-- See
Hello,
I'm currently developing some applications with explicit threading
using forkIO and have strange behaviour on my freshly installed Ubuntu
Karmic 9.10 (Kernel 2.6.31-14 SMP).
Setup:
Machine A: Quadcore, Ubuntu 9.04, Kernel 2.6.28-13 SMP
Machine B: AMD Opteron 875, 8 cores, 2.6.18-164
Hello,
I'm currently developing some applications with explicit threading
using forkIO and have strange behaviour on my freshly installed Ubuntu
Karmic 9.10 (Kernel 2.6.31-14 SMP).
Setup:
Machine A: Quadcore, Ubuntu 9.04, Kernel 2.6.28-13 SMP
Machine B: AMD Opteron 875, 8 cores, 2.6.18-164
