Maybe I'm getting to old for this kind of fiddeling around.
I tend to believe what you are saying, sometimes I have trouble remembering the basics ...
What do I conclude out of this?
Well, NO MORE POSTS from me, I guess !
Cheers
. . Just my 2c worth, not having installed a new BOINC for quite a while, is it possible that during the setup there was a selection between local preferences and network preferences and you chose local?
<core_client_version>7.16.6</core_client_version>
<![CDATA[
<stderr_txt>
12:12:26 (26533): [normal]: This Einstein@home App was built at: Aug 17 2021 16:19:40
Petri stated his normal runtime is around 120 seconds so he is running only 1X per gpu or maybe possibly 2X if he is running a new bit of tweaked code.
The fact that one ran 1200 seconds is anomaly that indicates the task got stuck somehow where the cpu couldn't service it correctly or that BOINC for some reason kept taking focus away from the task instead of processing it normally.
Petri stated his normal runtime is around 120 seconds so he is running only 1X per gpu or maybe possibly 2X if he is running a new bit of tweaked code.
The fact that one ran 1200 seconds is anomaly that indicates the task got stuck somehow where the cpu couldn't service it correctly or that BOINC for some reason kept taking focus away from the task instead of processing it normally.
. . Yep. I felt sure he normally runs onesies. But that task ran as an 8sie (see the line I highlighted in the message). I won't even try to guess why but it did ...
Good catch, I missed that in your quote. If you look at his current set of valid tasks, he is running onesies as you call it.
How that one task got switched to eightsies 0.13 gpu resource is a mystery.
. . Is that the theme from Twilight Zone I hear in the background. ... ???
:)
Stephen
PS: Have you noticed a change in run times on tasks sent out since about 2am today UTC?? On both of my serious crunchers run times have dropped from around 10 mins to about 8.5 mins consistently.
. . I just had a peek at your machine with the 2070s and the same thing is happening on it. Run times were 298 and 278 for the two cards, but now they are 262 and 246. Something has changed. I wondered if maybe there had been an unrequested upgrade of the video drivers but not when I checked my machines.
Thank you Stephen and Keith! I did a test and ran 8 tasks per GPU at a time. It did not yield to any speed-up. I had forgotten that and did not check the GPU % (0.13).
I noticed that the task times have dropped: 15 sec off on my TITAN V and about 17 sec off on my RTX 2080 Ti
San-Fernando-Valley
)
. . Just my 2c worth, not having installed a new BOINC for quite a while, is it possible that during the setup there was a selection between local preferences and network preferences and you chose local?
Stephen
petri33 wrote:Hi,my
)
. . Hi Petri,
. . Do you normally run 8sies? (My term for 8 concurrent tasks).
. . 8 x 124 = 992; 8 x 179= 1432. OR 1224 / 8 = 153 ... ???
Stephen
Petri stated his normal
)
Petri stated his normal runtime is around 120 seconds so he is running only 1X per gpu or maybe possibly 2X if he is running a new bit of tweaked code.
The fact that one ran 1200 seconds is anomaly that indicates the task got stuck somehow where the cpu couldn't service it correctly or that BOINC for some reason kept taking focus away from the task instead of processing it normally.
Keith Myers wrote: Petri
)
. . Yep. I felt sure he normally runs onesies. But that task ran as an 8sie (see the line I highlighted in the message). I won't even try to guess why but it did ...
Stephen
Good catch, I missed that in
)
Good catch, I missed that in your quote. If you look at his current set of valid tasks, he is running onesies as you call it.
How that one task got switched to eightsies 0.13 gpu resource is a mystery.
All I can think of is he was editing his app_info and had a case of fat fingers and entered the anomalous value.
Then corrected it. But if that was the case he would have known of the error and not posted the message about "what happened here"
Keith Myers wrote:Good
)
. . Is that the theme from Twilight Zone I hear in the background. ... ???
:)
Stephen
PS: Have you noticed a change in run times on tasks sent out since about 2am today UTC?? On both of my serious crunchers run times have dropped from around 10 mins to about 8.5 mins consistently.
<scratching head>
. . I just had a peek at
)
. . I just had a peek at your machine with the 2070s and the same thing is happening on it. Run times were 298 and 278 for the two cards, but now they are 262 and 246. Something has changed. I wondered if maybe there had been an unrequested upgrade of the video drivers but not when I checked my machines.
Stephen
<head scratching furiously now>
Thank you Stephen and Keith!
)
Thank you Stephen and Keith! I did a test and ran 8 tasks per GPU at a time. It did not yield to any speed-up. I had forgotten that and did not check the GPU % (0.13).
I noticed that the task times have dropped: 15 sec off on my TITAN V and about 17 sec off on my RTX 2080 Ti
--
Petri
petri33 wrote: I noticed
)
yeah looks like we’re running the faster 3011 tasks. The 4011 series tasks we’ve been on for a while are a bit slower.
_________________________________________________________________________
Hmm, no sign of fast running
)
Hmm, no sign of fast running 3011's here. Just the usual 4013's
[Edit] Damn Einstein's sorting preference. See them now.