![]() ![]() I understand that there is a certain … uncertainty and you cannot expectĪn exact one-to-one of the actual measured CPU Load and the configured CPU Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread. Because of the scheduling policy, thread could run less that 0.5 seconds because there was more prioritized thread in the system, or it could run a little bit more than 0.5 seconds, because OS missed the exact moment to put the thread on sleep mode.Īnd even more: there is no clear way to see exact CPU usage of some particular process, at least with standard tools of OS. There is no way to tell OS to run some thread some particular amount of time, for example 0.5 seconds. If you set CPU usage to 30%, BOINC will run 0.3 seconds at 100% giving in total 30% of CPU usage. So if we set CPU usage to 50%, BOINC will run 0,5 seconds at 100% of CPU giving in total 50% of CPU usage. Limiting CPU time means limiting a time when application actually run. My actual experience is, that for almost all configured values „cpu_usage_limit" the actual load is more or less out of scope and only very few settings will really hit the spot … I have to admit the I only have this one MPB for „testing“ so it might be a „local“ problem of my particular configuration.Īm um 17:15 schrieb Vitalii Koshura afraid, your calculations are a little bit wrong. so it’s actually using only half of what it should use, which is quite the opposite of the 1% setting.Īgain, I would agree in a +/- 5% difference of the configured value due to the technical reasons you described. Right now I’m running BOINC with 30% cpu_usage_limit and my actual CPU load is 12%. However, what I really measured was a 70% CPU load over 10 minutes in average. In other words, we can safely assume that the CPU should be idling at least 90% of the time with this setting. Very likely the actual load is less since the eight threads will be executed not all at the same time. So, as far as my humble knowledge of hardware goes, even in a worst case the CPU should be 100% busy only one second out of 100 in case all eight BOINC tasks will be processed at the very same time. Let’s assume a 100 second window … if I understand you right, BOINC will run a given task for 1 second within that 100 second window and obviously we cannot predict at which point in time this will happen exactly. Just today I configured BOINC with 1% CPU usage to test my suspicion. I have an MBP mid-2015 running macOS Mojave 10.14.6 with an eight core i7, 16GB RAM, BOINC 7.16.6, three projects and all cores allowed to be used resulting in currently 8 tasks. I understand that there is a certain … uncertainty and you cannot expect an exact one-to-one of the actual measured CPU Load and the configured CPU usage in BOINC … But … Thank you very much for your quick response. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |