Set no CPU tasks but still getting CPU tasks?

Randomacts
Randomacts
Joined: 26 Mar 16
Posts: 11
Credit: 2,439,561
RAC: 0
Topic 198539

I'm really confused why this is the case.

Holmis
Joined: 4 Jan 05
Posts: 996
Credit: 697,916,972
RAC: 723,107

Set no CPU tasks but still getting CPU tasks?

Have you created different preferences for different locations/venues, aka home, school, work? And have you changed prefs for the right location?

Randomacts
Randomacts
Joined: 26 Mar 16
Posts: 11
Credit: 2,439,561
RAC: 0

RE: Have you created

Quote:
Have you created different preferences for different locations/venues, aka home, school, work? And have you changed prefs for the right location?

I haven't messed with those at all because I don't switch settings locations ect

Is that seriously what the issue is?

Edit: That can't be an issue because I only have the 'default' group .. I just checked.

Although the stuff that seem to matter is in the first picture... I may as well show this as well

Holmis
Joined: 4 Jan 05
Posts: 996
Credit: 697,916,972
RAC: 723,107

RE: Is that seriously what

Quote:
Is that seriously what the issue is?


Apparently no, I just started out with the simplest thing I could think of.

I've now looked a bit closer and these are my findings so far:
You have 3 computers attached to Einstein@home.

One is a Linux host that doesn't appear to have any usable GPU, at least it's not reported so opting out of CPU work will result in this host not being able to get any tasks from Einstein@home at all.

One is a Windows host with a Intel HD4400 GPU, this host will only get GPU work if you either change the GPU-driver to an older version, version 10.18.10.3906 is the maximum. Or you could opt in to "run test applications".
Be aware thought that there are a lot of reports about difficulties finding a driver version newer than the max above that produces valid results. Check this lengthy thread for more info.

The third host is a Windows host with a Nvidia GTX560Ti and the prefs should work for this host, as to why the prefs for not getting CPU tasks didn't work on this host I don't know and the last contact log don't show anything useful at the moment. We will have to wait until the host asks for more work before we can continue investigating.
The only thing I can think of right now is that you were assigned some CPU tasks before you changed settings and they somehow got lost, then the server resent them as lost tasks to your host, this process ignores the current settings.

Oh and welcome to Einstein@home, I hope that either I or someone else around here can help you get this sorted so that you'll have a nice time here! =)

Christian Beer
Christian Beer
Moderator
Joined: 9 Feb 05
Posts: 595
Credit: 96,904,763
RAC: 1

As Holmis already explained.

As Holmis already explained. The Use CPU flag is set for every new user. The first host you attach will always ask for CPU work as this setting is in effect. Until you disable the flag you will continue to get CPU tasks and also get resends if you don't abort them. Depending on when you changed the settings and when your Client updated them your host downloaded some CPU work. You should not get new CPU work assigned from now on.

Randomacts
Randomacts
Joined: 26 Mar 16
Posts: 11
Credit: 2,439,561
RAC: 0

RE: RE: Is that seriously

Quote:
Quote:
Is that seriously what the issue is?

Apparently no, I just started out with the simplest thing I could think of.

I've now looked a bit closer and these are my findings so far:
You have 3 computers attached to Einstein@home.

One is a Linux host that doesn't appear to have any usable GPU, at least it's not reported so opting out of CPU work will result in this host not being able to get any tasks from Einstein@home at all.

One is a Windows host with a Intel HD4400 GPU, this host will only get GPU work if you either change the GPU-driver to an older version, version 10.18.10.3906 is the maximum. Or you could opt in to "run test applications".
Be aware thought that there are a lot of reports about difficulties finding a driver version newer than the max above that produces valid results. Check this lengthy thread for more info.

The third host is a Windows host with a Nvidia GTX560Ti and the prefs should work for this host, as to why the prefs for not getting CPU tasks didn't work on this host I don't know and the last contact log don't show anything useful at the moment. We will have to wait until the host asks for more work before we can continue investigating.
The only thing I can think of right now is that you were assigned some CPU tasks before you changed settings and they somehow got lost, then the server resent them as lost tasks to your host, this process ignores the current settings.

Oh and welcome to Einstein@home, I hope that either I or someone else around here can help you get this sorted so that you'll have a nice time here! =)

It seems that all of the cpu tasks on the windows PC (don't worry about the strangler other clients I'll deal with those later and it is a pain to change tasks since I can't get boinc tasks working so I use just boincstats)

Anyways it seems that the issue.. might have been 'Gravitational Wave search O1 all-sky F' ones .. I disabled that and hopefully I should be good now?

Only time will tell prob.

Holmis
Joined: 4 Jan 05
Posts: 996
Credit: 697,916,972
RAC: 723,107

Hmm... This seems a bit

Hmm...

This seems a bit strange, @13:49:56 UTC Randomacts edited in the pictures in the third post in this thread, @14:27:57 UTC 3 X64O1F-tasks was assigned to the Windows host #12225338
I didn't see this until after 14:30:11 UTC when the host last made contact with the server so I missed the log for when the CPU tasks were assigned.

The "Use CPU" flag should have prevented those tasks from being sent.

@Christian
Might there be a bug in the scheduler with regards to honoring the "Use CPU" flag set to "No" when deciding whether or not to send Gravity wave tasks, considering that we now use a new way of handling these tasks?

@Randomacts
I would disable the following items in "Run only the selected applications" as they are CPU only:
Gravitational Wave search O1 all-sky F
Gravitational Wave search O1 all-sky I
Gamma-ray pulsar search #4
Gamma-ray pulsar binary search #1

Randomacts
Randomacts
Joined: 26 Mar 16
Posts: 11
Credit: 2,439,561
RAC: 0

RE: Hmm... This seems a

Quote:

Hmm...

This seems a bit strange, @13:49:56 UTC Randomacts edited in the pictures in the third post in this thread, @14:27:57 UTC 3 X64O1F-tasks was assigned to the Windows host #12225338
I didn't see this until after 14:30:11 UTC when the host last made contact with the server so I missed the log for when the CPU tasks were assigned.

The "Use CPU" flag should have prevented those tasks from being sent.

@Christian
Might there be a bug in the scheduler with regards to honoring the "Use CPU" flag set to "No" when deciding whether or not to send Gravity wave tasks, considering that we now use a new way of handling these tasks?

@Randomacts
I would disable the following items in "Run only the selected applications" as they are CPU only:
Gravitational Wave search O1 all-sky F
Gravitational Wave search O1 all-sky I
Gamma-ray pulsar search #4
Gamma-ray pulsar binary search #1

Thanks I'll disable those

Edit: on a side note typical of the intel gpus my w10 laptop is being a bit of a pain to get working with the gpu side.. but I'll deal with this more later.. I remember a post about not all gpu verisons work? I just tried updating to the latest driver in w10 15.40 and hopefully that fixed it.

Christian Beer
Christian Beer
Moderator
Joined: 9 Feb 05
Posts: 595
Credit: 96,904,763
RAC: 1

RE: Hmm... This seems a

Quote:

Hmm...

This seems a bit strange, @13:49:56 UTC Randomacts edited in the pictures in the third post in this thread, @14:27:57 UTC 3 X64O1F-tasks was assigned to the Windows host #12225338
I didn't see this until after 14:30:11 UTC when the host last made contact with the server so I missed the log for when the CPU tasks were assigned.

The "Use CPU" flag should have prevented those tasks from being sent.

@Christian
Might there be a bug in the scheduler with regards to honoring the "Use CPU" flag set to "No" when deciding whether or not to send Gravity wave tasks, considering that we now use a new way of handling these tasks?

Nope. They were resends but the sent time got updated ( a feature I didn't know of):

2016-03-29 14:27:57.8913 [PID=7793 ]    [send] [RESULT#552655906] [HOST#12225338] (resend lost work)
2016-03-29 14:27:57.8930 [PID=7793 ]    [send] est. duration for WU 242865466: unscaled 14725.41 scaled 15051.16
2016-03-29 14:27:57.8931 [PID=7793 ]    [HOST#12225338] Sending [RESULT#552655906 h1_0058.95_O1C01Cl2In3__O1AS20-100F_59.05Hz_841_1] (est. dur. 15051.16 seconds, delay 1209600, deadline 1460471277)


The original assignment was done: 2016-03-26 14:32:36.6180 [PID=5995 ] [HOST#12225338] Sending [RESULT#552655906 h1_0058.95_O1C01Cl2In3__O1AS20-100F_59.05Hz_841_1] (est. dur. 15109.92 seconds, delay 1209600, deadline 1460212356)

Resend lost work is usually triggered after a project reset on the Client. The tasks in progress and waiting are not aborted when clicking reset. If you don't want CPU work please abort it, so someone else can get it.

Randomacts
Randomacts
Joined: 26 Mar 16
Posts: 11
Credit: 2,439,561
RAC: 0

RE: Nope. They were

Quote:

Nope. They were resends but the sent time got updated ( a feature I didn't know of):

2016-03-29 14:27:57.8913 [PID=7793 ]    [send] [RESULT#552655906] [HOST#12225338] (resend lost work)
2016-03-29 14:27:57.8930 [PID=7793 ]    [send] est. duration for WU 242865466: unscaled 14725.41 scaled 15051.16
2016-03-29 14:27:57.8931 [PID=7793 ]    [HOST#12225338] Sending [RESULT#552655906 h1_0058.95_O1C01Cl2In3__O1AS20-100F_59.05Hz_841_1] (est. dur. 15051.16 seconds, delay 1209600, deadline 1460471277)

The original assignment was done: 2016-03-26 14:32:36.6180 [PID=5995 ] [HOST#12225338] Sending [RESULT#552655906 h1_0058.95_O1C01Cl2In3__O1AS20-100F_59.05Hz_841_1] (est. dur. 15109.92 seconds, delay 1209600, deadline 1460212356)

Resend lost work is usually triggered after a project reset on the Client. The tasks in progress and waiting are not aborted when clicking reset. If you don't want CPU work please abort it, so someone else can get it.

Hmm well this does still leave me with 2 issues.

Issue #1 is I can't figure out how to make android be allowed to use CPUs because I can't set a location for it... (I can just find another CPU project I guess... but my main CPU project vLHC@home doesn't run on android for obvious reasons.

Issue #2 I still need to get the igpu working on my laptop but that is a more fixable issue as there are several thread about that.. needing some exact driver.

mikey
mikey
Joined: 22 Jan 05
Posts: 5,120
Credit: 518,686,098
RAC: 89,289

RE: Issue #1 is I can't

Quote:

Issue #1 is I can't figure out how to make android be allowed to use CPUs because I can't set a location for it... (I can just find another CPU project I guess... but my main CPU project vLHC@home doesn't run on android for obvious reasons.

Can you just setup a different venue, ie work, home or school and put just the android in it? That way it has it's own parameters for what work to get and what not to get as well.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.