| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 15
|
|
| Author |
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges:
|
Also seeing this on an Intel i5 chip — since people are mentioning AMD — while ARP1, HST1, OPN1 are running smoothly together (without MIP1 disturbing the peace) on that laptop, while it's running Fedora (Linux) 33, which is the most recent version.
Been seeing this since 2020-11-27. Stopped acquiring MIP1 that same day on that device. I thought trying my luck today again, but to no avail. Maybe there's insufficient memory … (8 threads, 6 MB RAM, 6 MB L3-cache). App CpuTime Elapsed Claimed Granted ModTime Exit Outc SentTime ReceivedTime NameProject Name: Microbiome Immunity ProjectPS- I have no problem dropping MIP1 from that device, 'cause it has been merrily crunching away on ARP1, HST1 and OPN1 since … well, since these three exist. |
||
|
|
sterl
Cruncher Joined: Jul 23, 2013 Post Count: 5 Status: Offline Project Badges:
|
I have noticed similar occurrences. I have an older AMD cpu, running Linux Mint 20.1. Only processing 2 WU at one time.Some units work fine, others do not.
There seems to be 2 issues, for those who do not; 1/ Some units do not pickup where they left off after a reboot, it just starts processing at 0hrs,0mins 2/ The other issue is when a unit is processing and after several hours the remaining time just keeps increasing. The only way to overcome this is a reboot and that work unit restarts at 0hrs,0mins. I am not sure if this is the same on other projects, maybe I will give it a try on others for a few days and see how it goes |
||
|
|
Bryn Mawr
Senior Cruncher Joined: Dec 26, 2018 Post Count: 385 Status: Offline Project Badges:
|
I have noticed similar occurrences. I have an older AMD cpu, running Linux Mint 20.1. Only processing 2 WU at one time.Some units work fine, others do not. There seems to be 2 issues, for those who do not; 1/ Some units do not pickup where they left off after a reboot, it just starts processing at 0hrs,0mins 2/ The other issue is when a unit is processing and after several hours the remaining time just keeps increasing. The only way to overcome this is a reboot and that work unit restarts at 0hrs,0mins. I am not sure if this is the same on other projects, maybe I will give it a try on others for a few days and see how it goes I have seen both of these symptoms in Rosetta where WUs only checkpoint at the end of a “decoy”. Occasionally you get a WU where the first decoy runs for a very long time. Any restart whilst it is running causes it to begin at the beguine and when it gets to within 10 minutes of the estimated time the remaining time just sticks at 10 minutes because it just does not know how long the decoy will take and therefore what percentage is actually complete. On the other hand, if the remaining time is actively increasing rather than staying stable could it be in a loop? |
||
|
|
Sgt.Joe
Ace Cruncher USA Joined: Jul 4, 2006 Post Count: 7847 Status: Offline Project Badges:
|
8 threads, 6 MB RAM, 6 MB L3-cache I have a feeling you meant 6gb RAM. Cheers
Sgt. Joe
*Minnesota Crunchers* |
||
|
|
adriverhoef
Master Cruncher The Netherlands Joined: Apr 3, 2009 Post Count: 2346 Status: Offline Project Badges:
|
8 threads, 6 MB RAM, 6 MB L3-cache I have a feeling you meant 6gb RAM. Cheers Of course it is 6 GB RAM! ![]() Thanks very much for spotting this error in my documentation that I copied to the forum here, Sgt.Joe! ![]() |
||
|
|
|