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: 3
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 679 times and has 2 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Task Timeout Times - computer taking too long

I have installed the agent on a Pentium2 400Mhz 128MB machine.

It is running a task for the HPF project that has now been running continuosly for over 5 days and is only 56% complete.

Is this going to timeout? At what point do the WCG servers decide
the task has been lost?

According to the systems requirements, this machine is unsuitable for FAAH project.
[Dec 7, 2005 10:22:59 AM]   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: Task Timeout Times - computer taking too long

Hello finiduck,
You are doing fine. The time limits for the HPF project are 2 weeks run time or 3 weeeks clock time. It looks as though you are going to finish with about 4 days to spare.

mycrofth
[Dec 7, 2005 12:04:06 PM]   Link   Report threatening or abusive post: please login first  Go to top 
retsof
Former Community Advisor
USA
Joined: Jul 31, 2005
Post Count: 6824
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: Task Timeout Times - computer taking too long

I have installed the agent on a Pentium2 400Mhz 128MB machine.

It is running a task for the HPF project that has now been running continuosly for over 5 days and is only 56% complete.

Is this going to timeout? At what point do the WCG servers decide
the task has been lost?

According to the systems requirements, this machine is unsuitable for FAAH project.
That's a fast running workunit. I have a pentium II/400 that recently went offline due to other problems. Two Rosetta workunits encountered over the last year ran for over 13 days each, very close to the timeout.

Yes, the average FA@H workunits are running longer than the average Rosetta workunits. There's a reason for that 550MHz requirement.
----------------------------------------
SUPPORT ADVISOR
Work+GPU i7 8700 12threads
School i7 4770 8threads
Default+GPU Ryzen 7 3700X 16threads
Ryzen 7 3800X 16 threads
Ryzen 9 3900X 24threads
Home i7 3540M 4threads50%
----------------------------------------
[Edit 2 times, last edit by retsof at Dec 7, 2005 12:52:22 PM]
[Dec 7, 2005 12:49:43 PM]   Link   Report threatening or abusive post: please login first  Go to top 
[ Jump to Last Post ]
Post new Thread