Posts by Eliovich Alexander & Yan

1) Questions and Answers : Windows : Something is wrong with N-Body Simulation: it counts units of 3538 gigaflops endlessly without progress (Message 76756) Posted 12 Jan 2024 by Eliovich Alexander & Yan Post: Thanks everyone for your valuable advice! And I still hope that the N-Body program will be improved and will not collapse at the slightest breath of wind...
2) Questions and Answers : Windows : Something is wrong with N-Body Simulation: it counts units of 3538 gigaflops endlessly without progress (Message 76751) Posted 10 Jan 2024 by Eliovich Alexander & Yan Post: As far as I can see, the program has really begun to work sustainably. Apparently, it is the frequent stops that drive her into closed loops. Thanks for the advice! But in general, this is a big drawback of the program that it's work is not sustainable enough and it couldn't not prevent processor overheating.
3) Questions and Answers : Windows : Something is wrong with N-Body Simulation: it counts units of 3538 gigaflops endlessly without progress (Message 76750) Posted 10 Jan 2024 by Eliovich Alexander & Yan Post: 1. Different cores have nothing to do with it -- exactly the same problem arises for my Ryzen 3700x (Windows 10 also). 2. I'll try setting the counting time to 100% and report the results. But, this is not a very good situation -- I set time to 85% to prevent the processor from overheating. Thank you so much
4) Questions and Answers : Windows : Something is wrong with N-Body Simulation: it counts units of 3538 gigaflops endlessly without progress (Message 76748) Posted 9 Jan 2024 by Eliovich Alexander & Yan Post: And I received an answer to the question of whether Einstein@Home has an influence. I froze Einstein, and counting of the N-Body unit went relatively quickly. But a few hours later I turned on Mozilla just for 30 minutes. This was enough for the unit to freeze to death again! Something is very wrong with MilkiWay N-Body!! P.S.I’ll emphasize once again that I haven’t seen any problems with tasks of 65 thousand gigaflops yet: the counting is going very quickly. It's strange that they are calculated much faster than 3 thousand gigaflops tasks (which also freeze)! P.P.S. And the site is frustratingly slow...
5) Questions and Answers : Windows : Something is wrong with N-Body Simulation: it counts units of 3538 gigaflops endlessly without progress (Message 76747) Posted 8 Jan 2024 by Eliovich Alexander & Yan Post: I already know the answer for last question: if you close the Boinc, stop all tasks, and later restart the Boinc -- the freeze will be removed alas only for a while
6) Questions and Answers : Windows : Something is wrong with N-Body Simulation: it counts units of 3538 gigaflops endlessly without progress (Message 76746) Posted 8 Jan 2024 by Eliovich Alexander & Yan Post: I think, something is seriously wrong with N-Body Simulation 1.83 (mt) when it counts units of 3538 gigaflops. The program freezes at a certain percentage of the work completed (7.583% in my case), does not progress for dozens of hours, and the processor is only 0.1% occupied. The Boinc writes that 1.5 hours of processor time were spent, but its total operating time is 14 hours or more! It feels like the program is in some kind of endless loop. This whole freezing situation persists even when the processor is doing nothing else! At the same time, the program calculates units of several tens of gigaflops quite cheerfully I have processor Intel Core I7-1255U 16 Gb DDR4-3200 1600 Mhz with Windows 10 Prof The same situation with processor Intel Pentium J3710 Braswell 8 Gb DDR3-1600 with Widows 10 Prof (freezing percentage is another, about 6%) I set in Boinc to use maximum 86% threads of my processor I7-1255U (10 cores, 12 threads) Maybe the MilkyWay@Home is hampered by the fact that tasks for Einstein@Home are being processed on the graphics card in parallel? (Einstein uses video card and half of one CPU thread) P.S. Here's one more thing: if you close the Boinc, stop all tasks, and after a few minutes start the Boinc again, the freeze will be removed. For a while or forever -- I don’t know yet