Posts by Anthony Ayiomamitis

1) Message boards : Number crunching : Machines runs out of units every few minutes (Message 63011) Posted 13 Jan 2015 by Anthony Ayiomamitis Post: BOINC Manager will always fetch new work after a completed task is uploaded. As a result, you should not have this problem unless no new tasks are available from the server for download. With my installation, it checks once again a minute later for another fetch in the event the first fetch failed.
2) Message boards : Number crunching : Machines runs out of units every few minutes (Message 63009) Posted 13 Jan 2015 by Anthony Ayiomamitis Post: Adrian, There is a similar thread elsewhere and it seems MW will only allow three tasks per core and irrespective of how slow or fast these will be processed. See the following: http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=3698 Anthony.
3) Message boards : Number crunching : High frequency of "Too many results (may be nondeterministic) Too many total results" (Message 62929) Posted 2 Jan 2015 by Anthony Ayiomamitis Post: Mike et al, Happy New Year! Following the suggestion above, I am delighted at the crunching which is taking place at the moment. I have a couple of questions for the group. I have two laptops with the same processor (Intel Duo Core 2.67 GHz P9600) but there is a notable difference in the "Measured Integer Speed" and in contrast to the "Measured Floating Point Speed" which is virtually identical between the two machines. The machine with the slower integer speed (5542.79 million ops/sec) is running Windows Vista 32-bit with 2 Gb RAM whereas the machine with the faster integer speed (8323.87 million ops/sec) has Windows 7 64-bit with 4 Gb RAM. Question 1: is the difference due to operating system and/or RAM? I do plan to clone the hard disk from my faster machine anyway for use in the slower machine but the intentions were originally different (to save reinstallation of various bits of other software) Question 2: for the purposes of the MW project, I would assume the floating point speed is what really matters and which is virtually identical between the two machines. Is this correct? Question 3: does the graphics card play a role in the measured integer speed (NVIDIA Quadro 160MVS vs Intel Graphics card with accelerator)? Thanks in advance for the invaluable assistance!
4) Message boards : Number crunching : High frequency of "Too many results (may be nondeterministic) Too many total results" (Message 62912) Posted 30 Dec 2014 by Anthony Ayiomamitis Post: I have another duo core machine arriving this week and which I plan to dedicate to MilkyWay@Home. Thanks again for advice!
5) Message boards : Number crunching : High frequency of "Too many results (may be nondeterministic) Too many total results" (Message 62911) Posted 30 Dec 2014 by Anthony Ayiomamitis Post: Many thanks for the advice and feedback. I will modify my preferences as you suggest!
6) Message boards : News : New Nbody version 1.46 (Message 62909) Posted 29 Dec 2014 by Anthony Ayiomamitis Post: I am losing a lot of tasks for the same reason due to "too many results". In looking at the output log from various users for a particular task, the reported results vary dramatically with no two results being the same. Many times a negative result is also very informative and users should at least be credited rather than being penalized with 0 credits.
7) Message boards : Number crunching : High frequency of "Too many results (may be nondeterministic) Too many total results" (Message 62907) Posted 29 Dec 2014 by Anthony Ayiomamitis Post: Four every four validated results, I am getting one invalid result due to "Too many results (may be nondeterministic) Too many total results" and which represents an approximate invalid rate of 20%. Are others experiencing similar invalidated rates and consequent loss of credits since these invalid results are not credited.
8) Message boards : News : New Nbody version 1.46 (Message 62897) Posted 27 Dec 2014 by Anthony Ayiomamitis Post: Although I have a lot of experience with BOINC, I am quite new to MilkyWay@Home. A couple of days ago I downloaded the latest version of the software for a first time installation on an old Pentium laptop (for testing purposes) as well as a fairly good duo core with 2.67 GHz P9600 chip. With the old Pentium, I do have two results which have completed successfully but are waiting validation. However, the third task which started has been stuck on 5.3% completed for over 19 hrs while the first two tasks suggest a maximum run time of about 10 hrs. This is the task of interest: de_nbody_12_20_orphan_sim_2_1413455402_1484793 .... it seems to be stuck in some sort of infinite loop since the elapsed time just keeps increasing while the percentage completed is stuck at 5.267%. I have paused the task and started another one and I will resume the former once the latter task completes. Of the fourteen tasks completed the past 15 hrs or so, four have been credited whereas the other ten are waiting validation and confirmation. Weird ratio to say the least since my result is amongst two other results for some of the completed tasks with no quorum yet.