Questions and Answers :
Wish list :
Yafu threads
Message board moderation
Author | Message |
---|---|
Technik007[CZ] Send message Joined: 19 Dec 11 Posts: 3 Credit: 50,625,726 RAC: 57,157 ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I have 32 logical cores cpu nad had 2 yafu task running 8cpu + 8cpu so half of cores were not utilized. Selected to receive YAFU-16t tasks and I got one YAFU-16t waiting to run on 32 cores ! Wunderfull. So I had to delete that task, set usage limits to 50% in boinc manager preferences and ask for task again and then set it back 100%. Hopefully I got what I wanted and my cpu was 100% utilized (not most of time of course but sheduled to). But I don't uderstand why yafu scheduller selects cores this way. Simillary I cannot choose in yafu project preferences cpu limit higher than 8 cores what is quite outdated and I have always got 3*8cpus tasks on 32cores cpu. And nothing more when cpu limit is set to 8cpus. |
mikey Send message Joined: 13 Apr 17 Posts: 17 Credit: 19,780,168 RAC: 146,864 ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
I have 32 logical cores cpu nad had 2 yafu task running 8cpu + 8cpu so half of cores were not utilized. Selected to receive YAFU-16t tasks and I got one YAFU-16t waiting to run on 32 cores ! You can always choose 'no limit' but yes if decide to limit the cores 8 is the highest and yes it needs to be updated to 32, though maybe not every number in between 8 and 32 |
![]() Volunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message Joined: 22 Aug 11 Posts: 747 Credit: 17,634,097 RAC: 16 ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
|
kotenok2000 Send message Joined: 4 Oct 20 Posts: 25 Credit: 1,077,241 RAC: 1,958 ![]() ![]() ![]() ![]() ![]() |
Is it possible to upgrade yafu from 1.34 to 2.10? |
kotenok2000 Send message Joined: 4 Oct 20 Posts: 25 Credit: 1,077,241 RAC: 1,958 ![]() ![]() ![]() ![]() ![]() |
Yafu 2 displays estimated time to completion for gnfs in factor.log unlike 1.34 ![]() |