Page 2 of 2
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Mon Aug 17, 2015 7:32 pm
by 7im
Due to software constraints (.Net) of the V7 client, only Win XP and newer can run V7.
Older Windows could still run v6, but would not get assigned the newer GPU cores.
You're covered.
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Mon Aug 17, 2015 9:58 pm
by ejsanyo
What are the minimum system requirements for the Core 21? On my little PC it ate all of the 2GB system memory and then continued by inflating of the swap file until the whole system is not hung!
So I can't even provide you any logs! Referring to another topic, you sure that 2GB is enough? AthlonXP 3200+ and Radeon R7 250.
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Mon Aug 17, 2015 10:18 pm
by Rel25917
I've seen core 21 use up to around 3.5GB to get the unit going, it settles down to around 1GB once running.
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Mon Aug 17, 2015 11:55 pm
by bruce
ejsanyo wrote:What are the minimum system requirements for the Core 21?
As Rel25917 suggests, Core_21 will use a lot more RAM while it's initializing than once it gets running. Unless you have too small a limitation on the size of the paging file, it will successfully start and then release most of that memory, continuing to run until it finishing.
As with all programs that temporarily use a lot of RAM, performance depends on how much real RAM you have, but with at least the
MINIMUM, it will still succeed.
Many of the proteins that FAH intends to study in the near future are larger than the ones that we've been studying, and Core_21 enables them to be studied.
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Tue Aug 18, 2015 2:35 am
by 7im
In short, minimum is rarely the recommended or optimal.
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Tue Aug 18, 2015 10:17 pm
by mpharrigan
7im is right. Minimal is not optimal. If this becomes a problem, please let us know and we will bump up the minimum
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Thu Aug 20, 2015 11:54 pm
by ejsanyo
Hmm, at this time Core 21 peak memory consumption has dropped to about 500MB on the same PC and about to 350MB once it started. Which gave me able to continue processing. On another computer all in the same way. Looks like they are fixed it!
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Fri Aug 21, 2015 3:34 pm
by Rel25917
You don't mention the projects you got, 9712 is small compared to other core 21 projects. I just got one and it had 1.5GB peak and currently 377MB.
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Fri Aug 21, 2015 3:56 pm
by ejsanyo
Rel25917 wrote:You don't mention the projects you got, 9712 is small compared to other core 21 projects. I just got one and it had 1.5GB peak and currently 377MB.
Yes you're right. Today, I've got the same heavy task as before. On the same computer with 2GB RAM. And it hung of course. The bad news is that it got the project by default. Option "client_type" was removed some time before.
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Fri Aug 21, 2015 11:48 pm
by bruce
As I implied earlier, Core_21 is expected to do some really heavy processing that works best with lots of RAM to get started and then it settles down to a much smaller allocation. Are you sure it's hung or just doing a lot of paging during that initial phase of processing?
mpharrigan did say they could limit assignments to hardware with a larger minimum. The real question is how much is "enough"
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Sat Aug 22, 2015 11:20 pm
by ejsanyo
bruce wrote:Are you sure it's hung or just doing a lot of paging during that initial phase of processing?
Initially the system jammed heavily and rattled by HDD. After the minute or more HDD became silent and the system was blocked at all. I began to believe that the case in my disk as such or in it's interface. So I switched HDD from SATA to IDE motherboard plug using the convertor. Well, now the client began to launch as before. But in the end it somehow was able to get out and began to compute fine using about 700 MB of RAM. And completed the task successfully. Maybe this is my SATA controller did not manage too massive swap traffic or it's a problem with a specific driver version. Who knows. nForce 6100-based MSI K9N6PGM. Not the best hardware for crunching, I know...
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Sun Aug 23, 2015 1:08 pm
by DutchForce
mpharrigan wrote:We're restricting the assignment server to only assign core21 projects to > xp
edit: to prevent unnecessary restriction, I've set it to make sure it's *not* windows xp. So you may still get an assignment on windows 98 or something, but then shame on you
After the restriction I have set the advanced flag again and did not get Core_21 WUs on my Win XP 64-bit system (did get a few P9704/9712 WUs on my other Win7 64-bit system).
But since yesterday I'm getting Core_21 (P9704 and 9712) WUs assigned to my Win XP 64-bit system again, so I don't know if there is something changed (only change I've seen is that P9704/9712 are moved to full FAH a few days ago) or that the restriction is not working properly ?
Re: Core_21 v11 (P9712) not working with Win XP 64-bit
Posted: Sun Aug 23, 2015 4:11 pm
by mpharrigan
I just double checked the settings. Nothing seems to have changed. I'll bother the devs to see why this might be happening