Single-thread performance of the T1-T3 CPUs is indeed very low compared with x86-CPUs. The T4 CPU catches up, hopefully the T6 will do the next big step!

Mit freundlichen Grüßen,

Rainer Herbst
Zentrale Einrichtung für Informations-
verarbeitung und Kommunikation (ZEIK)
Universität Potsdam
Am Neuen Palais 10, Haus 8, Zimmer 0.70a
14469 Potsdam
Tel. 0331 - 977 1039


Quoting Jersey Man <jerse...@yahoo.com>:

Wondering if anyone has any insights

I have a simple bash script which spawns many (~1000) processes in a while loop - each goes into background
On Debian/Sparc the time taken for each iteration gets delayed every loop

The same script on X64/RHEL simply flies... Are there any throttling limits on Debian which may be slowing process creation. Getting a 1000 such process takes over an 1 1/2 on Debian/Sparc while on the X64 server it takes about 1/3 the time. Both servers have identical memory and the CPUs are Niagara T1 vs XEON 4 CPU

Or is the XEON so much faster?



real    0m1.250s
user    0m1.232s
sys    0m0.012s
Background mode - PID=[16619]

real    0m1.377s
user    0m1.224s
sys    0m0.028s
Background mode - PID=[16628]

real    0m1.323s
user    0m1.232s
sys    0m0.020s
Background mode - PID=[16637]

...

real    0m1.640s
user    0m1.232s
sys    0m0.016s
Background mode - PID=[16674]

real    0m1.515s
user    0m1.236s
sys    0m0.012s
Background mode - PID=[16683]

...

real    0m1.934s
user    0m1.236s
sys    0m0.012s
Background mode - PID=[16773]

real    0m2.132s
user    0m1.224s
sys    0m0.024s
Background mode - PID=[16782]

real    0m2.134s
user    0m1.216s
sys    0m0.028s
Background mode - PID=[16791]

....

real    0m3.426s
user    0m1.232s
sys    0m0.016s
Background mode - PID=[17125]

...

real    0m4.112s
user    0m1.236s
sys    0m0.012s
Background mode - PID=[17252]




--
To UNSUBSCRIBE, email to debian-sparc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20130828085254.ijc496g34swoo...@webmail.uni-potsdam.de

Reply via email to