{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":63395302,"defaultBranch":"main","name":"blogstuff","ownerLogin":"randomascii","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2016-07-15T05:52:34.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/10800041?v=4","public":true,"private":false,"isOrgOwned":false},"refInfo":{"name":"","listCacheKey":"v0:1605989914.0","currentOid":""},"activityList":{"items":[{"before":"bf824686a50e89dfdf2c6fa2bd195b68f9b9cda5","after":"bb46864ad9a510c6756b50d6faf106fe3f4591d9","ref":"refs/heads/main","pushedAt":"2023-10-02T03:21:26.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"randomascii","name":"Bruce Dawson","path":"/randomascii","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/10800041?s=80&v=4"},"commit":{"message":"Improve background test code\n\nThis change improves the background test code so that it runs repeatedly\nin normal mode and then background mode. It always runs for about 1,000\nms (rather than needing configuration variables) and after each\nbackground-mode run it prints the ratio. Thus, compiling and running\nthis provides an estimate of the slowdown caused by background mode in\nthis test case. It is... considerable. And surprisingly variable.","shortMessageHtmlLink":"Improve background test code"}},{"before":"21aa65f27fafc016842a7775e6a625ce0515a510","after":"bf824686a50e89dfdf2c6fa2bd195b68f9b9cda5","ref":"refs/heads/main","pushedAt":"2023-09-27T05:36:03.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"randomascii","name":"Bruce Dawson","path":"/randomascii","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/10800041?s=80&v=4"},"commit":{"message":"Test code for PROCESS_MODE_BACKGROUND_BEGIN\n\nWhen a process is put into background mode with this command:\n  SetPriorityClass(GetCurrentProcess(), PROCESS_MODE_BACKGROUND_BEGIN);\n\nthen the following happens, per Microsoft's documentation:\n\n  Begin background processing mode. The system lowers the\n  resource scheduling priorities of the process (and its threads) so\n  that it can perform background work without significantly affecting\n  activity in the foreground.\n  This value can be specified only if hProcess is a handle to the\n  current process. The function fails if the process is already in\n  background processing mode.\n\nIt's a big vague but the overall idea is clear - this should lower the\nimpact of the process on the system.\n\nHowever, this can be hugely inaccurate. One effect of this call is to\nlimit the working set of the process to 32 MiB. If the process touches\nmore memory than this then the kernel will repeatedly fault in pages and\ntrim the working set, causing work to take about 300 times as long to\nrun. In other words, the CPU load in this scenario will be dramatically\n_increased_.\n\nTherefore, this call should never be used.\n\nThis test code demonstrates this problem. Run it with and without the\n\"background\" parameter to see the difference in performance.","shortMessageHtmlLink":"Test code for PROCESS_MODE_BACKGROUND_BEGIN"}}],"hasNextPage":false,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAADjRNH7QA","startCursor":null,"endCursor":null}},"title":"Activity · randomascii/blogstuff"}