Good morning Clinton,
On the following machine
Times reported below reflect averages over three executions.
Expect 20 minutes for suite to run to completion.
Word Size Main Memory C Compiler clockOS
32 bit 972 MB gcc 4.4.7 1.0 GHz UNIX
CPU
4x Intel(R) Atom(TM) CPU N570 @ 1.66GHz
Elapsed time h:m:s |Concurrent |
benchmark |Sequential| |Concurrent|
|Performance|
concord concord.dat 13.453N/A
deal 5 11.879N/A
ipxref ipxref.dat7.263N/A
queens 1215.564N/A
rsg rsg.dat 12.733N/A
binary-trees 14 19.274
the current runtimes are about 10 slower than the example given.
Mind you, the bench marks are stalling on
binary-trees 14
at the moment.
Both runs have stalled at
binary-trees 14 19.274
I'll keep it running while outside and have a look later at where the
problem seems to be.
regards
Bruce Rennie
On 12/04/17 04:51, Jeffery, Clint (jeffe...@uidaho.edu) wrote:
>
> Thanks to everyone who sent me benchmarks.
>
>
> Things I've noticed:
>
>
> 1. Unicon 13 is generally faster than Unicon 12. Range is 5% to 400%,
> typical might be 70-80%.
>
> 2. We improved our calculation of CPU clock speed on Linux; need to
> develop one on MacOS.
>
> 3. Some Concurrent benchmarks run slower than sequential on some
> folks' machines. Range is 6x slowdown to 12x speedup.
>
> I think it is fair to say some pthreads implementations are
> better than others, and some CPUs better than others for threading.
>
> The range of numbers will also be helpful for future study.
>
>
> Clint
>
>
>
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>
>
> ___
> Unicon-group mailing list
> Unicon-group@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/unicon-group
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Unicon-group mailing list
Unicon-group@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unicon-group
