+- +-
Say hello if visiting :) by Gecko
11 Jan 2023, 07:43:05 pm

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: GPU crunching question  (Read 132128 times)

BiddySlayer

  • Guest
Re: GPU crunching question
« Reply #135 on: 26 May 2007, 10:48:44 am »
8800GTS 640MB, C2D E6600, Windows 2000

I ran both versions

The 1st one ran for about 8 minutes, crashed at powerspectrum 0.000274345. cpu at 50% while running and after crash.

2nd version crash straight away. cpu left at 50%

1st stderr.txt attached

[attachment deleted by admin]

BiddySlayer

  • Guest
Re: GPU crunching question
« Reply #136 on: 26 May 2007, 10:49:44 am »
Here is the 2nd stderr.txt

Keep up the good work

[attachment deleted by admin]

Offline Devaster

  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 653
  • I like Duke !!!
Re: GPU crunching question
« Reply #137 on: 26 May 2007, 11:01:18 am »
today when i come to home i ll upload next tp with corrected fftlenght and with exception traps so youll see what happen...

Offline Devaster

  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 653
  • I like Duke !!!
Re: GPU crunching question
« Reply #138 on: 26 May 2007, 03:12:03 pm »
as i have wrote : next technology preview :

1. corrected lenght of fft
2. added exception traps for rapidmind

at the begining you will see some messages from rapidmind platform - performance log - about uploading and binding datas

usage as before - unpack,stop and close boinc,run exe with - standalone and wait ....

[attachment deleted by admin]
« Last Edit: 26 May 2007, 03:17:40 pm by Devaster »

Offline Simon

  • Ni!
  • Knight who says 'Ni!'
  • *****
  • Posts: 1045
    • Is it a bird? Is it a plane? No...its-the.net!
Re: GPU crunching question
« Reply #139 on: 26 May 2007, 03:54:34 pm »
Here's a test run on my Athlon64 3500+ 2.2GHz single core with an ATI Radeon X800RX.

I've attached the stdout, stderr and result.sah for you - by the way, are you using a -9 (Result overflow) WU on purpose so it stays short? May not be the best way to test with, but I'm not sure. Maybe Joe can tell.

Finished pretty quickly even with such a comparatively slow card.

Regards,
Simon.

[attachment deleted by admin]

Offline Vyper

  • Alpha Tester
  • Knight Templar
  • ***
  • Posts: 376
Re: GPU crunching question
« Reply #140 on: 26 May 2007, 04:02:28 pm »
Simon -> "Finished pretty quickly even with such a comparatively slow card."

How quick is quick in this case? :)

//Vyper

Offline Simon

  • Ni!
  • Knight who says 'Ni!'
  • *****
  • Posts: 1045
    • Is it a bird? Is it a plane? No...its-the.net!
Re: GPU crunching question
« Reply #141 on: 26 May 2007, 04:10:23 pm »
I'll have to do another run to be sure.

Here's another run from my laptop in the meantime - 3.06 GHz P4 mobile, 1GB DDR333, Radeon 9600 Pro mobile.

Regards,
Simon.

<edit>The run on the A64 took 3 Minutes 6 seconds, on the laptop more than 10 minutes (estimated). CPU usage on both hosts was 100%, both 32 bit XP.</edit>

[attachment deleted by admin]
« Last Edit: 26 May 2007, 04:27:47 pm by Simon »

Offline Vyper

  • Alpha Tester
  • Knight Templar
  • ***
  • Posts: 376
Re: GPU crunching question
« Reply #142 on: 26 May 2007, 04:26:01 pm »
The app itself setiathome.xxxx.exe consumed about 6 minutes in cputime in the processmeter in windows.. 6 minutes and 2 seconds then it closes up. (The app itself never consumed more than 50% , and systemprocess fiddled up and down from 12-42% aprox).. The cpu was never used 100% on both cores!

Core2Duo (Overclocked to 3.3 ghz), Vista X64, 8800GTX (Orig clocks)

File included with stderr etc..

//Vyper

P.S Damn! (That was fast times on the A64 though, wonder if Vista X64 does something) Nice..



[attachment deleted by admin]
« Last Edit: 26 May 2007, 04:31:12 pm by Vyper »

Offline Vyper

  • Alpha Tester
  • Knight Templar
  • ***
  • Posts: 376
Re: GPU crunching question
« Reply #143 on: 26 May 2007, 04:40:46 pm »
I compared the result.sah file from both your hosts and they produce the same result, mine differ alot in all values compared to yours from the A64 and the laptop ..

Seems really like a Vista or x64 issue in this case, really odd indeed..

Update:  I tried that particular W/U with a regular Kwsn 2.2B SSSE3 client, it took about 3 minutes and completed without errors (The -9 error) so the code needs some polishing but it completes though..

//Vyper
« Last Edit: 26 May 2007, 05:12:39 pm by Vyper »

BiddySlayer

  • Guest
Re: GPU crunching question
« Reply #144 on: 26 May 2007, 05:28:08 pm »
completed in 4 minutes 30 seconds.

result.sah and stderr attatched

[attachment deleted by admin]

Offline Devaster

  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 653
  • I like Duke !!!
Re: GPU crunching question
« Reply #145 on: 27 May 2007, 12:26:26 am »
full 100 % usage of cpu is only on older cards and a single core CPU

Neoman

  • Guest
Re: GPU crunching question
« Reply #146 on: 27 May 2007, 02:51:16 am »
System: E6600@3.6G 8800GTX(core612/mem2000) under Vista64
The cpu usage was 62% and it took more than 10 minutes to complete i guess. :o

resuilt.sah and stderr attached.

[attachment deleted by admin]

Offline Devaster

  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 653
  • I like Duke !!!
Re: GPU crunching question
« Reply #147 on: 27 May 2007, 03:08:10 am »
ill try compile new exe for 64-bit os  ;)
maybe there is the problem ....

DJXaeR0

  • Guest
Re: GPU crunching question
« Reply #148 on: 27 May 2007, 04:48:58 am »
X2 3800+ @ 2650mhz, 8800 GTX, XP32

[attachment deleted by admin]

pepperammi

  • Guest
Re: GPU crunching question
« Reply #149 on: 27 May 2007, 02:44:23 pm »
Pentium D945 @ 3.6Ghz, Nvidia 7950GT 512MB oc'ed edition, Vista x64 Ultimate with just about everything turned off for the run.

Didn't get stuck like did last time which is brilliant to see. CPU usage through first part about 25-65% all together (sorry didin't take note of cpu on the app alone) and ~22% through second half for just the app itself. 
Took something like 10 minutes for me too but still great to see working. Incredible work.

[attachment deleted by admin]

 

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: 59559
Total Topics: 1672
Most Online Today: 355
Most Online Ever: 983
(20 Jan 2020, 03:17:55 pm)
Users Online
Members: 0
Guests: 49
Total: 49
Powered by EzPortal