+- +-
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: It works!  (Read 28529 times)

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: It works!
« Reply #15 on: 25 Feb 2009, 11:48:04 am »
Well I waited an hour, and it never finsihed. I can certainly plug the app in again and watch the state.dat when it freezes.  It seems to be a regular occurance at least with this particular app, and Boinc combination (And I do suspect Boinc's scheduling behaviour is to blame pretty strongly).

Shouldn't take long.


Offline Raistmer

  • Working Code Wizard
  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 14349
Re: It works!
« Reply #16 on: 25 Feb 2009, 11:55:49 am »
I need to know if "refuse to die" mod works or not. If it not work indeed I remove it from CUDA MB.

So I need next info on this topic:

1) When CUDA MB processed task enters in "waiting to run" mode what tasks are in "running" mode ?
2) What access state of GPU_lock file (is it accessible or not)
3) Is any progress inside state.sah of task being in "waiting" state.
4) How many CUDA MB processes running in system at this time
5) temp of GPU (busy or idle).


Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: It works!
« Reply #17 on: 25 Feb 2009, 12:04:20 pm »
I can answer most of those now, will update remaining ones at next lockup

....
So I need next info on this topic:

1) When CUDA MB processed task enters in "waiting to run" mode what tasks are in "running" mode ?
    2 x AP 5.03 on CPU cores
2) What access state of GPU_lock file (is it accessible or not)
     ...
3) Is any progress inside state.sah of task being in "waiting" state.
     ...
4) How many CUDA MB processes running in system at this time
     1 on only GPU, 'Waiting to Run'
5) temp of GPU (busy or idle).
    Busy, Full load temp  ~75C  ( not overheating for this GPU either, no screen jerkyness or other apparent issue, can still run ATI Tool with no Artifacts)

Offline Raistmer

  • Working Code Wizard
  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 14349
Re: It works!
« Reply #18 on: 25 Feb 2009, 12:19:10 pm »

4) How many CUDA MB processes running in system at this time
     1 on only GPU, 'Waiting to Run'

I meant OS processes, not BOINC ones.

And it seems you don't use ncpus field? why only 2 AP tasks on dual core + GPU ?

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: It works!
« Reply #19 on: 25 Feb 2009, 12:21:14 pm »
Read original my post again.  I tried both ways.  If you want me to do this with ncpus=3 .. will do.

Offline Geek@Play

  • Alpha Tester
  • Knight Templar
  • ***
  • Posts: 330
Re: It works!
« Reply #20 on: 25 Feb 2009, 12:43:12 pm »
1) When CUDA MB processed task enters in "waiting to run" mode what tasks are in "running" mode ?
   At this time I would have 4 AstroPulse work units running on 4 CPU cores.

2) What access state of GPU_lock file (is it accessible or not)
   I do not have this file or where it is at.  Only have "boinc_lockfile" located in slots folders.

3) Is any progress inside state.sah of task being in "waiting" state.
   Included here are 2 state files captured several minutes apart.

4) How many CUDA MB processes running in system at this time
   Only the one (1) that is showing "waiting to run" in Boinc Manager.

5) temp of GPU (busy or idle).
   65C busy, 56C idle.

[attachment deleted by admin]
Boinc....Boinc....Boinc....Boinc

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: It works!
« Reply #21 on: 25 Feb 2009, 12:54:25 pm »
Okay,

 switched to ncpus = 3, and whammo! .. stuck at 1.712% ... ( I reckon some kindof oversubscription mechanism is at play here )
[Filling in answers as I gather the data]
[Edit:] Now while collecting info, this one jumped from 1.712% to 100%, looks completed
 - AR is 0.443445
-  Claimed credit says ~1.94 credit  ???
-  wall time in stderr ~18mins 20 secs. (~Typical full length run)
http://setiathome.berkeley.edu/result.php?resultid=1172313302

Quote
1) When CUDA MB processed task enters in "waiting to run" mode what tasks are in "running" mode ?
  3 x AP 5.03 (1 per CPU core +1 )
2) What access state of GPU_lock file (is it accessible or not)
Opens as empty file in notepad without complaint.
3) Is any progress inside state.sah of task being in "waiting" state.
  Not visibly, though timestamp was incrementing every checkpoint period etc
4) How many CUDA MB processes running in system at this time
Only the 1 'Waiting to run"
5) temp of GPU (busy or idle).
Busy 75C (normal), if run ATITool at same time, no artefacts.
« Last Edit: 25 Feb 2009, 01:17:39 pm by Jason G »

Offline Raistmer

  • Working Code Wizard
  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 14349
Re: It works!
« Reply #22 on: 25 Feb 2009, 01:14:01 pm »
1) When CUDA MB processed task enters in "waiting to run" mode what tasks are in "running" mode ?
   At this time I would have 4 AstroPulse work units running on 4 CPU cores.

2) What access state of GPU_lock file (is it accessible or not)
   I do not have this file or where it is at.  Only have "boinc_lockfile" located in slots folders.

3) Is any progress inside state.sah of task being in "waiting" state.
   Included here are 2 state files captured several minutes apart.

4) How many CUDA MB processes running in system at this time
   Only the one (1) that is showing "waiting to run" in Boinc Manager.

5) temp of GPU (busy or idle).
   65C busy, 56C idle.

state.sah1
<prog>0.23420485</prog>

state.sah2
<prog>0.29913810</prog>

That is, task in that slot continue to make progress. It seems all as intended to be.
Now it would be interesting to watch until <prog> value reaches to 1 - what will be with BOINC in this case.

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: It works!
« Reply #23 on: 25 Feb 2009, 01:19:56 pm »
Okay, so why the massive 1.94 credit claim on my full length no progress run ? (See updated run info)

It seems there are no function calls to accumulate the flops while it is running. (compute_fraction_done or whatever Cuda app uses) [Edit: It will be interesting to see what the Wingman Claims).
« Last Edit: 25 Feb 2009, 01:25:01 pm by Jason G »

Offline Geek@Play

  • Alpha Tester
  • Knight Templar
  • ***
  • Posts: 330
Re: It works!
« Reply #24 on: 25 Feb 2009, 01:24:14 pm »
Ageless posted here............

http://setiathome.berkeley.edu/forum_thread.php?id=52090&nowrap=true#869394

This may be a Boinc problem?  If so my apologies to Raistmer.
Boinc....Boinc....Boinc....Boinc

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: It works!
« Reply #25 on: 25 Feb 2009, 01:29:09 pm »
Ageless posted here............

http://setiathome.berkeley.edu/forum_thread.php?id=52090&nowrap=true#869394

This may be a Boinc problem?  If so my apologies to Raistmer.

That was the first suspicion I mentioned (Boinc cpu scheduling foulups) But after experiencing it I'm not so sure.  It may simply be not receiving the updated flops counts for whatever reason.  Hopefully it is their problem not ours  ;)

Offline Raistmer

  • Working Code Wizard
  • Volunteer Developer
  • Knight who says 'Ni!'
  • *****
  • Posts: 14349
Re: It works!
« Reply #26 on: 25 Feb 2009, 01:33:51 pm »
Okay, so why the massive 1.94 credit claim on my full length no progress run ? (See updated run info)

It seems there are no function calls to accumulate the flops while it is running. (compute_fraction_done or whatever Cuda app uses) [Edit: It will be interesting to see what the Wingman Claims).
LoL  You know , I never cared about credits much ;D
But it's interesting indeed why it can't accumulate flops in this case... very interesting.
But except credit question all just work as intended! BOINC tried to leave your GPU IDLE (it started only CPU apps ) but CUDA app resisted and made use GPU at least until it finished its work. All possibilities to keep GPU busy were used!

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: It works!
« Reply #27 on: 25 Feb 2009, 01:44:03 pm »
LoL... Yeah, something's busted though for this weird behaviour.  Boinc or app doesn't matter.

Running 3 AP's has my system rather oversubscribed it seems, so throughput was quite a bit better running 2 APs rather than 3.

Will be reverting to my 'classic' setup, and if that doesn't work, will consider pawning my PC for beer money  :P  [Damn it's working no beer for me  ;) ]

Jason
« Last Edit: 25 Feb 2009, 01:55:40 pm by Jason G »

Offline Richard Haselgrove

  • Messenger Pigeon
  • Knight who says 'Ni!'
  • *****
  • Posts: 2819
Re: It works!
« Reply #28 on: 25 Feb 2009, 02:00:51 pm »

[Damn it's working no beer for me  ;) ]

Jason


I'm sure we can sort something out if you join Matt on his tour of Lancashire, Yorkshire, Nottinghamshire, Cambridgeshire.... :P

Offline Jason G

  • Construction Fraggle
  • Knight who says 'Ni!'
  • *****
  • Posts: 8980
Re: It works!
« Reply #29 on: 25 Feb 2009, 02:09:12 pm »
I'm sure we can sort something out if you join Matt on his tour of Lancashire, Yorkshire, Nottinghamshire, Cambridgeshire.... :P

If that's the tour where we all travel through townships cross country in a yellow combi-van wearing poncho's and funny hats, stopping at every pub along the way, Count Me In!  ;D

 

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: 48
Most Online Ever: 983
(20 Jan 2020, 03:17:55 pm)
Users Online
Members: 0
Guests: 39
Total: 39
Powered by EzPortal