| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Completed Research
Forum: FightAIDS@Home Phase 2
Thread: New FAH2-version in production |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 14
|
|
| Author |
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1316 Status: Offline Project Badges: 
|
Keith Uplinger wrote in the FAHB Beta thread:
----------------------------------------Greetings everyone, Thank you again for testing the workunits. I have done the extra check after the minor input tweak. We are promoting them to production. Thanks, -Uplinger New versions 7.30 On Linux it's using a bit more memory and much more virtual memory as already was remarked during the Beta test. Previous version Linux: FAH2_001691_avx40816-0-1_000002_000011_172_0 7.28 FightAIDS@Home Phase2 Virt. Memory 128.95 MB Memory 70.07 MB Actual version Linux: FAH2_001344_avx101124-3_000008_000058_193_0 7.30 FightAIDS@Home Phase2 Virt. Memory 1324.89 MB Memory 164.14 MB  [Edit 2 times, last edit by Crystal Pellet at Jan 25, 2019 10:32:30 AM] |
||
|
|
Aurum
Master Cruncher The Great Basin Joined: Dec 24, 2017 Post Count: 2384 Status: Offline Project Badges: 
|
What really matters is what is the deadline. Is it still the ridiculous 24 hours???
----------------------------------------  ...KRI please cancel all shadow-banning |
||
|
|
Dayle Diamond
Senior Cruncher Joined: Jan 31, 2013 Post Count: 450 Status: Offline Project Badges: 
|
Yes, and they're about four times longer.
Hopefully that means four times fewer iterations, and experiments don't stay in limbo for nearly a year anymore. |
||
|
|
Rickjb
Veteran Cruncher Australia Joined: Sep 17, 2006 Post Count: 666 Status: Offline Project Badges: 
|
Under Windows, these new WUs are showing memory requirements of about 250 - 300 MB each, vs 80 - 100MB for the previous ones.
----------------------------------------The new program is blocked from running under XP - see discussion of this in the Beta thread: FightAIDS@Home Phase 2 Beta Test Dec 26, 2018 [ Issues Thread ] . uplinger said there:"Howdy, I have some bad news about the support for Windows XP. We are not supporting Windows XP for WCG projects." The posts there by Apis Tintinnambulator re. XP may be of interest. [Edit 1 times, last edit by Rickjb at Jan 27, 2019 10:55:36 AM] |
||
|
|
Magiceye04
Cruncher Joined: Jul 5, 2008 Post Count: 36 Status: Offline Project Badges: 
|
... On Linux it's using a bit more memory and much more virtual memory as already was remarked during the Beta test. Thats a bit underestimated. On my 16GB machine each WU claimes 2GB and to run more than 14 WUs at the same time is not possible any more unless i stop all other work. And the credits were going drastically down. old: 1h ~35cr new: 4,5h ~80cr. [Edit 1 times, last edit by magiceye04 at Jan 26, 2019 10:50:55 PM] |
||
|
|
Crystal Pellet
Veteran Cruncher Joined: May 21, 2008 Post Count: 1316 Status: Offline Project Badges:
|
... On Linux it's using a bit more memory and much more virtual memory as already was remarked during the Beta test. Thats a bit underestimated. On my 16GB machine each WU claimes 2GB and to run more than 14 WUs at the same time is not possible any more unless i stop all other work. My first remark was with the shorter running FAH2's. Meanwhile we have much longer running ones (10.5 hours) and they claim indeed more virtual memory and real memory. I also have 14 tasks running with only 9500MB RAM available. Host not used for something else. Virtual memory between 1949MB and 1969MB and memory between 529MB and 551MB. Edit: Mem: 9725296k total, 8561632k used, 1163664k free, 91812k buffers [Edit 1 times, last edit by Crystal Pellet at Jan 27, 2019 10:38:08 AM] |
||
|
|
Kenneth
Cruncher Netherlands Joined: Oct 9, 2009 Post Count: 20 Status: Offline Project Badges: 
|
24 hours deadline is really not enough, I have switched many non-top-specs machines to other projects.
|
||
|
|
True54Blue
Advanced Cruncher Joined: Nov 17, 2004 Post Count: 97 Status: Offline Project Badges: 
|
Agreed on 24 hours being too short. It's taking my machines 8 to 12 hours real time for each WU. I've just received my first error for not returning a result in time. What a waste that was as it was still processing. I'm receiving over 200 points per result though so that seems ok.
---------------------------------------- |
||
|
|
Magiceye04
Cruncher Joined: Jul 5, 2008 Post Count: 36 Status: Offline Project Badges:
|
Even my very old and very slow Athlon5350 has no problems to crunch a WU in 10h.
It should be clear that this project is nothing for machines that do not run more than 15h /day. There are a lot more projects. :) |
||
|
|
TOMinAZ
Cruncher United States Joined: Feb 11, 2007 Post Count: 40 Status: Offline Project Badges: 
|
I have an older HP Pavilion laptop which I used to let run 1 WU at a time, it usually took about 4-5 hours. This past weekend, I saw estimated run time was over 12 hours. I had to abort the WU, since I wouldn't have finished before the deadline. The next day, I let it download another WU, and saw the same estimated run time. I aborted that WU also.
My quad core desktop shows a dramatic increase in run time, too. But those WUs run in about 4 hours (previously a bit over an hour). That's quite the increase. |
||
|
|
|