C117 seen

Author	Message
yoyo_rkn Volunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message Joined: 22 Aug 11 Posts: 725 Credit: 16,445,605 RAC: 1	Message 729 - Posted: 14 Nov 2014, 18:34:34 UTC The workunit generator decided to take some C117 numbers. Take care once they are sent out. ID: 729 · Rating: 0 · rate: / Reply Quote

Speedy51 Send message Joined: 25 Jan 12 Posts: 23 Credit: 1,529,974 RAC: 9	Message 741 - Posted: 24 Nov 2014, 3:05:16 UTC Last modified: 24 Nov 2014, 3:06:52 UTC I have been processing if you work units of late & I notice we are working on C 111. Are we starting to process lower numbers again? Or is this a case of the feeder selecting wrong numbers again? I have included a couple of work units as examples 238594 Could you please also note that the CPU time and run time for this task is incredibly close together/there is less than an hour's difference between the 2 is this normal. Could this also happened if I have another CPU intensive applications running at the same time? 238593 ID: 741 · Rating: 0 · rate: / Reply Quote

yoyo_rkn Volunteer moderator Project administrator Project developer Project tester Volunteer developer Volunteer tester Project scientist Send message Joined: 22 Aug 11 Posts: 725 Credit: 16,445,605 RAC: 1	Message 742 - Posted: 24 Nov 2014, 5:16:47 UTC - in response to Message 741. You can see here http://factorization.ath.cx/stat_1.php on which level how many workunits are available. The wu generator chooses them randomly. Additional new numbers are added by scientists. So it will happen, that also lower number are in the queue. ID: 742 · Rating: 0 · rate: / Reply Quote

Speedy51 Send message Joined: 25 Jan 12 Posts: 23 Credit: 1,529,974 RAC: 9	Message 743 - Posted: 24 Nov 2014, 7:08:59 UTC Thank you for the link very helpful information. ID: 743 · Rating: 0 · rate: / Reply Quote