+- +-
Say hello if visiting :) by Mike
23 Apr 2021, 08:55:37 am

Seti is down again by Mike
09 Aug 2017, 10:02:44 am

Some considerations regarding OpenCL MultiBeam app tuning from algorithm view by Raistmer
11 Dec 2016, 06:30:56 am

Loading APU to the limit: performance considerations by Mike
05 Nov 2016, 06:49:26 am

Better sleep on Windows - new round by Raistmer
26 Aug 2016, 02:02:31 pm

Author Topic: New 2.4L version for linux x86  (Read 7002 times)

Offline Crunch3r

  • Knight who says 'Ni!'
  • *****
  • Posts: 602
    • 64 bit boinc clients
New 2.4L version for linux x86
« on: 14 Sep 2007, 02:25:44 pm »
Hello,

i've updated the 32 bit linux apps and those work for 2.4 & 2.6 Kernels.

Some changes:
- new SSE2 app is for both Intel and AMD cpus
- added FFTW builds for SSE & SSE2


Download: http://calbe.dw70.de/seti.html

regards
Crunch3r

I want to share something with you: The three little sentences that will get you through life. Number 1: Cover for me. Number 2: Oh, good idea, Boss! Number 3: It was like that when I got here.

Homer Simpson

Offline michael37

  • Knight o' The Round Table
  • ***
  • Posts: 137
Re: New 2.4L version for linux x86
« Reply #1 on: 15 Sep 2007, 10:41:20 am »
I updated the benchmark benchmark.  Since my computers are dual-core or dual-CPU, I added the "taskset" statement to enforce CPU affinity to CPU #2. 
  • If your computer has only one CPU, just remove "taskset 0x2" from the script.
  • If your computer has multiple CPUs and has no taskset command, install it. 
  • Ubuntu: sudo apt-get schedutils. 
  • Red Hat/Novell: download and install schedutils RPM.




[attachment deleted by admin]

Offline michael37

  • Knight o' The Round Table
  • ***
  • Posts: 137
FM workunits on Intel Core 2
« Reply #2 on: 15 Sep 2007, 10:43:41 am »
---------------------------------------------------
Starting benchmark run...
---------------------------------------------------
Current WU: FM0017.wu
---------------------------------------------------
Running default app 2.4L_x32_SSE.bin...
Time for 2.4L_x32_SSE.bin: 616.122505 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2.bin....
Time for 2.4L_x32_SSE2.bin: 590.852925 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE3.bin....
Time for 2.4L_x32_SSE3.bin: 587.076689 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE2.bin....
Time for 2.4L_x64_SSE2.bin: 573.211823 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE3.bin....
Time for 2.4L_x64_SSE3.bin: 567.859489 seconds
Validation Result: strongly similar.
---------------------------------------------------
Done with FM0017.wu.

Current WU: FM0446.wu
---------------------------------------------------
Running default app 2.4L_x32_SSE.bin...
Time for 2.4L_x32_SSE.bin: 622.686915 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2.bin....
Time for 2.4L_x32_SSE2.bin: 602.869677 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE3.bin....
Time for 2.4L_x32_SSE3.bin: 592.453025 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE2.bin....
Time for 2.4L_x64_SSE2.bin: 594.405148 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE3.bin....
Time for 2.4L_x64_SSE3.bin: 586.636661 seconds
Validation Result: strongly similar.
---------------------------------------------------
Done with FM0446.wu.

Current WU: FM1181.wu
---------------------------------------------------
Running default app 2.4L_x32_SSE.bin...
Time for 2.4L_x32_SSE.bin: 549.598347 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2.bin....
Time for 2.4L_x32_SSE2.bin: 526.472901 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE3.bin....
Time for 2.4L_x32_SSE3.bin: 520.124505 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE2.bin....
Time for 2.4L_x64_SSE2.bin: 521.104566 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE3.bin....
Time for 2.4L_x64_SSE3.bin: 509.639850 seconds
Validation Result: strongly similar.
---------------------------------------------------
Done with FM1181.wu.



Offline michael37

  • Knight o' The Round Table
  • ***
  • Posts: 137
MB workunit on Intel Core 2
« Reply #3 on: 15 Sep 2007, 10:44:20 am »
---------------------------------------------------
Starting benchmark run...
---------------------------------------------------
Current WU: MB1399.wu
---------------------------------------------------
Running default app 2.4L_x32_SSE.bin...
Time for 2.4L_x32_SSE.bin: 1868.088748 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2.bin....
Time for 2.4L_x32_SSE2.bin: 1639.530464 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE3.bin....
Time for 2.4L_x32_SSE3.bin: 1590.939427 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE2.bin....
Time for 2.4L_x64_SSE2.bin: 1551.648972 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE3.bin....
Time for 2.4L_x64_SSE3.bin: 1566.977929 seconds
Validation Result: strongly similar.
---------------------------------------------------
Done with MB1399.wu.

Done with Benchmark run!

Offline michael37

  • Knight o' The Round Table
  • ***
  • Posts: 137
FM workunits on AMD Opteron (SSE2 is OK, no SSE3 support)
« Reply #4 on: 15 Sep 2007, 10:49:06 am »
---------------------------------------------------
Starting benchmark run...
---------------------------------------------------
Current WU: FM0017.wu
---------------------------------------------------
Running default app 2.4L_x32_SSE.bin...
Time for 2.4L_x32_SSE.bin: 778.439305 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2.bin....
Time for 2.4L_x32_SSE2.bin: 731.759305 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE3.bin....
./benchmark: line 98: 15303 Illegal instruction     taskset 0x2 $BENCH_APP
Time for 2.4L_x32_SSE3.bin: 308.899305 seconds
Validation Result: different!
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE2.bin....
Time for 2.4L_x64_SSE2.bin: 844.319305 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE3.bin....
./benchmark: line 98: 15303 Illegal instruction     taskset 0x2 $BENCH_APP
Time for 2.4L_x64_SSE3.bin: 308.899305 seconds
Validation Result: different!
---------------------------------------------------
Done with FM0017.wu.

Current WU: FM0446.wu
---------------------------------------------------
Running default app 2.4L_x32_SSE.bin...
Time for 2.4L_x32_SSE.bin: 787.219305 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2.bin....
Time for 2.4L_x32_SSE2.bin: 760.619305 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE3.bin....
./benchmark: line 98: 15303 Illegal instruction     taskset 0x2 $BENCH_APP
Time for 2.4L_x32_SSE3.bin: 308.899305 seconds
Validation Result: different!
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE2.bin....
Time for 2.4L_x64_SSE2.bin: 904.039305 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE3.bin....
./benchmark: line 98: 15303 Illegal instruction     taskset 0x2 $BENCH_APP
Time for 2.4L_x64_SSE3.bin: 308.899305 seconds
Validation Result: different!
---------------------------------------------------
Done with FM0446.wu.

Current WU: FM1181.wu
---------------------------------------------------
Running default app 2.4L_x32_SSE.bin...
Time for 2.4L_x32_SSE.bin: 824.289305 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2.bin....
Time for 2.4L_x32_SSE2.bin: 746.869305 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE3.bin....
./benchmark: line 98: 15277 Illegal instruction     taskset 0x2 $BENCH_APP
cp: cannot stat `state.sah': No such file or directory
Time for 2.4L_x32_SSE3.bin: 308.899305 seconds
Validation Result: different!
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE2.bin....
Time for 2.4L_x64_SSE2.bin: 1078.649305 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE3.bin....
./benchmark: line 98: 15303 Illegal instruction     taskset 0x2 $BENCH_APP
cp: cannot stat `state.sah': No such file or directory
Time for 2.4L_x64_SSE3.bin: 308.899305 seconds
Validation Result: different!
---------------------------------------------------
Done with FM1181.wu.


Offline michael37

  • Knight o' The Round Table
  • ***
  • Posts: 137
MB workunit on AMD Opteron
« Reply #5 on: 15 Sep 2007, 03:18:51 pm »
This computer runs 64-bit RHEL4 with 2.4.21 kernel.

---------------------------------------------------
Starting benchmark run...
---------------------------------------------------
Current WU: MB1399.wu
---------------------------------------------------
Running default app 2.4L_x32_SSE.bin...
Time for 2.4L_x32_SSE.bin: 3658.289305 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2.bin....
Time for 2.4L_x32_SSE2.bin: 3168.299305 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x64_SSE2.bin....
Time for 2.4L_x64_SSE2.bin: 5322.109305 seconds
Validation Result: strongly similar.
---------------------------------------------------
Done with MB1399.wu.

Done with Benchmark run!

speedy67

  • Guest
Re: New 2.4L version for linux x86
« Reply #6 on: 04 Nov 2007, 08:03:38 pm »
The new 2.4L app are averaging about 7% slower than the previous R-2.4|xW apps on my AMD Athlon64 3000+ running Ubuntu/2.6.15-29-server...

Greetings,
Sander

elec999

  • Guest
Re: New 2.4L version for linux x86
« Reply #7 on: 18 Nov 2007, 04:17:46 pm »
Links seem down.
Thanks

sancio

  • Guest
Bench on Athlon 64 X2 4400+
« Reply #8 on: 22 Feb 2008, 09:19:18 am »
I used KWSN-Bench-Linux with new benchmark script,
tested with testWU 1 and 2.
Where are MB wu?

Results:

new 2.4L seems better than old 2.4  8)
good job...thanks, thanks, thanks   ;D

SSE3 ok but slow,
FFTW more slow than stock,
the best for my system: SSE2.
Now I'm installing it.

Here you can see results for this computer, now 14 with stock client.

Code: [Select]
---------------------------------------------------
Starting benchmark run...
---------------------------------------------------
Current WU: testWU-2.wu
---------------------------------------------------
Running default app default-527...
Time for default-527: 796.937804 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4_x32k2.6_AMD_SSE2.bin....
Time for 2.4_x32k2.6_AMD_SSE2.bin: 709.408334 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4_x32k2.6_Intel_SSE3f.bin....
Time for 2.4_x32k2.6_Intel_SSE3f.bin: 718.608909 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE.bin....
Time for 2.4L_x32_SSE.bin: 730.501653 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2.bin....
Time for 2.4L_x32_SSE2.bin: 689.643099 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2_FFTW.bin....
Time for 2.4L_x32_SSE2_FFTW.bin: 829.543843 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE3.bin....
Time for 2.4L_x32_SSE3.bin: 701.139818 seconds
Validation Result: strongly similar.
---------------------------------------------------
Done with testWU-2.wu.

Current WU: testWU-1.wu
---------------------------------------------------
Running default app default-527...
Time for default-527: 753.663100 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4_x32k2.6_AMD_SSE2.bin....
Time for 2.4_x32k2.6_AMD_SSE2.bin: 667.417710 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4_x32k2.6_Intel_SSE3f.bin....
Time for 2.4_x32k2.6_Intel_SSE3f.bin: 680.430524 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE.bin....
Time for 2.4L_x32_SSE.bin: 691.835236 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2.bin....
Time for 2.4L_x32_SSE2.bin: 653.708854 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE2_FFTW.bin....
Time for 2.4L_x32_SSE2_FFTW.bin: 794.409647 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE3.bin....
Time for 2.4L_x32_SSE3.bin: 671.229949 seconds
Validation Result: strongly similar.
---------------------------------------------------
Done with testWU-1.wu.

Done with Benchmark run!

sancio

  • Guest
OLD Celeron (Coppermine) 700 SSE1 (Toshiba S1700-500)
« Reply #9 on: 22 Feb 2008, 09:39:13 am »
Best SSE1, FFTW too slow.

Code: [Select]
---------------------------------------------------
Starting benchmark run...
---------------------------------------------------
Current WU: testWU-1.wu
---------------------------------------------------
Running default app default-527...
Time for default-527: 2617.139560 seconds
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4_x32k2.6_SSE.bin....
Time for 2.4_x32k2.6_SSE.bin: 2229.755351 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE.bin....
Time for 2.4L_x32_SSE.bin: 2165.775352 seconds
Validation Result: strongly similar.
---------------------------------------------------
---------------------------------------------------
Running S@H app 2.4L_x32_SSE_FFTW.bin....
Time for 2.4L_x32_SSE_FFTW.bin: 2651.833729 seconds
Validation Result: strongly similar.
---------------------------------------------------
Done with testWU-1.wu.

Done with Benchmark run!

 

Welcome, Guest.
Please login or register.
 
 
 
Forgot your password?
Members
Total Members: 97
Latest: ToeBee
New This Month: 0
New This Week: 0
New Today: 0
Stats
Total Posts: 59558
Total Topics: 1672
Most Online Today: 12
Most Online Ever: 983
(20 Jan 2020, 03:17:55 pm)
Users Online
Members: 0
Guests: 8
Total: 8
Powered by EzPortal