Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 126
Posts: 126   Pages: 13   [ Previous Page | 4 5 6 7 8 9 10 11 12 13 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 21056 times and has 125 replies Next Thread
Sgt.Joe
Ace Cruncher
USA
Joined: Jul 4, 2006
Post Count: 7581
Status: Recently Active
Project Badges:
Reply to this Post  Reply with Quote 
Re: Starting OET1 "OM" type workunits

I am not seeing many repair units. I have exactly 1 in 5 pages of "in progress" units.
Cheers
----------------------------------------
Sgt. Joe
*Minnesota Crunchers*
[Apr 23, 2018 12:41:45 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: Starting OET1 "OM" type workunits

Currently have 147 OM units in execution across 14 machines and all are _0 except (4) _1 and (1) _2. Wus average 5 to 7 hours execution time. All machines are reliable with a 1 day caches. Have almost twice that many waiting execution with 90% _0.

I could be wrong but it seems like the techs did respond concerning the CreatProcess failure and indicated the percentage of errors was too small to justify any correction activities. They would continue to monitor
----------------------------------------
[Edit 1 times, last edit by Doneske at Apr 23, 2018 3:01:40 PM]
[Apr 23, 2018 2:56:25 PM]   Link   Report threatening or abusive post: please login first  Go to top 
hchc
Veteran Cruncher
USA
Joined: Aug 15, 2006
Post Count: 747
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Starting OET1 "OM" type workunits

...caused by some Windows 8.1 machines with client 7.2.47...

Those clients might not actually be running on Windows 8.1. The 7.2.47 client doesn't identify Windows 10 correctly and reports it as Windows 8.1.


I dug a little and corroborated this.

In my Results Status, one of the WUs that's been aborted by user was listed as: Microsoft Windows 8.1 Core x64 Edition, (06.03.9600.00)
but in the debug log for that client does in fact reveal it to be Win10:
File Version : 10.0.16299.15 (WinBuild.160101.0800)
Company Name : Microsoft Corporation
Product Name : Microsoft® Windows® Operating System
Product Version : 10.0.16299.15


Interesting. So that tells me that the issue is not with "Windows 8.1" (actually Win10) clients running 7.2.47 but with 7.2.47 itself, potentially not being able to handle Windows 10 and Erroring out constantly. Which means the solution is for WCG and users to get their acts together and keep current with the latest BOINC client.
----------------------------------------
  • i3-8100 (Coffee Lake, 4C/4T) @ 3.6 GHz
  • i5-4590 (Haswell, 4C/4T) @ 3.3 GHz
  • E5800 (Wolfdale, 2C/2T) @ 3.2 GHz

----------------------------------------
[Edit 1 times, last edit by hchc at Apr 27, 2018 4:35:20 AM]
[Apr 24, 2018 1:42:22 AM]   Link   Report threatening or abusive post: please login first  Go to top 
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1671
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Starting OET1 "OM" type workunits

After one chaotic month, it seems that OET1 is recovering with more reliable estimation and fair granted credit.
Since a couple of days, we are close to the situation we have before OM WUs have been released, excepted that these WUs take at least 4x to 5x more time than the non-OM WUs.
Cheers,
Yves
----------------------------------------
[Apr 26, 2018 8:02:44 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Procyon Lotor One
Cruncher
Joined: Jun 28, 2008
Post Count: 14
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Starting OET1 "OM" type workunits

There is a 37% of the project remaining so I think you will be okay in terms of run-time. How many days do you average per calendar day?

I get about 14 to 15 per calendar day with my three host.


At 14.9 days per calendar day it will take you 24.49 days to achieve one year sums 365 divided by 14.9 = 24.49. How many months will it take you to reach your goal?

I am 16 years 317 days into the 20-year badge. So, I guess I need about ten months at this point. I was doing a bit better on the days average per calendar day - but it has dropped off (as has my Efficiency and Gflops).
[Apr 27, 2018 7:05:37 AM]   Link   Report threatening or abusive post: please login first  Go to top 
TPCBF
Master Cruncher
USA
Joined: Jan 2, 2011
Post Count: 1932
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Starting OET1 "OM" type workunits

Interesting. So that tells me that the issue is not with "Windows 8.1" (actually Win10) clients running 7.2.47 but with 7.2.47 itself, potentially not being able to handle Windows 10 and Erroring out constantly. Which means the solution is for WCG and users to get their acts together and keep current with the latest BOINC client.
I am running WCG/BOINC on a lot of Windows 10 machines. Most of them are the WCG 7.2.47 version. With no ill effects, even a couple that are crunching Einstein (that started to complain about the version recently). To prevent it becoming a problem for those (and all of those on which it is an inactive "backup" project), I updated manually a few hosts to the latest BOINC version from Berkley (7.8.3), just in case Einstein was just giving an early heads-up. No change in anything but a different icon.

As far as OET WUs goes, I haven't seen (as m)any of the 39.4 credit WUs recently, but overall, with only minor changes in the (number of) hosts that are crunching WCG (as has always been the case for the years I am participating in WCG), the average daily credit has decreased from the high 50,000s to the mid/high 30,000s, which would be a 35-40% decrease. And all the while the average runtime per day, after a short dip during the transition to the longer WUs, is more or less steady at 80-85 days of runtime per calendar day... thinking

Ralf
----------------------------------------

[Apr 27, 2018 8:01:28 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Speedy51
Veteran Cruncher
New Zealand
Joined: Nov 4, 2005
Post Count: 1265
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Starting OET1 "OM" type workunits

There is a 37% of the project remaining so I think you will be okay in terms of run-time. How many days do you average per calendar day?

I get about 14 to 15 per calendar day with my three host.


At 14.9 days per calendar day it will take you 24.49 days to achieve one year sums 365 divided by 14.9 = 24.49. How many months will it take you to reach your goal?

I am 16 years 317 days into the 20-year badge. So, I guess I need about ten months at this point. I was doing a bit better on the days average per calendar day - but it has dropped off (as has my Efficiency and Gflops).

All the best with your goal. At the time of the post the project is 65 % complete
----------------------------------------

[Apr 28, 2018 12:40:07 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Dayle Diamond
Senior Cruncher
Joined: Jan 31, 2013
Post Count: 450
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Starting OET1 "OM" type workunits

I'm hoping that's not the real estimate. Long time ago, IIRC, a tech estimated that the OM units alone would take about six months. We're doing the remaining units out of batch order. Hopefully we can wrap up this project so there's throughput for the three new climate modeling projects WCG has announced.
[Apr 30, 2018 11:56:49 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Speedy51
Veteran Cruncher
New Zealand
Joined: Nov 4, 2005
Post Count: 1265
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Starting OET1 "OM" type workunits

I am currently running OET1_0000644_xSDGP-OM_rig_96427_2 on Windows 10 using Boinc client 7.8.3 jobs started and it said it had over 2 days remaining it has done about 2 1/4 hours and is at roughly 28 % done saying it has 1 day 13 hours 33 minutes remaining. I have no doubt the job will finish in time. I am curious to whether other people have seen this with these work units before?? I noticed it only happens with one job in the list all the jobs have 4 day deadline. Due on the 17th at 9:23.28 AM
----------------------------------------

[May 13, 2018 10:04:20 PM]   Link   Report threatening or abusive post: please login first  Go to top 
TPCBF
Master Cruncher
USA
Joined: Jan 2, 2011
Post Count: 1932
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Starting OET1 "OM" type workunits

I am currently running OET1_0000644_xSDGP-OM_rig_96427_2 on Windows 10 using Boinc client 7.8.3 jobs started and it said it had over 2 days remaining it has done about 2 1/4 hours and is at roughly 28 % done saying it has 1 day 13 hours 33 minutes remaining. I have no doubt the job will finish in time. I am curious to whether other people have seen this with these work units before?? I noticed it only happens with one job in the list all the jobs have 4 day deadline. Due on the 17th at 9:23.28 AM
Get this quite frequently that jobs are downloaded with an initial estimated runtime of +1d, but almost all, beside some older dual cores, finish the jobs in the 8-20h range.
The WU that you listed ends in _2, which means it is a resend, those always have a shorter deeadline than "regular" WUs (_0)...

Ralf
----------------------------------------

[May 13, 2018 11:37:03 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 126   Pages: 13   [ Previous Page | 4 5 6 7 8 9 10 11 12 13 | Next Page ]
[ Jump to Last Post ]
Post new Thread