4 ms·

100% CPU: My Fault?

• grouphugs 5y ago
  window's main problem is the dns-client and dns-cache atm. the threat actors are actually u.s. government agencies blaming china. the main issue with all of this is nazi's controlling technology, as always. set dns manually, disable dns-client via registry ``` REG add “HKLM\SYSTEM\CurrentControlSet\services\dnscache” /v Start /t REG_DWORD /d 4 /f ``` better yet, stop using nazi technology (psych, the oss world is actually mostly white supremacists and racists atm, from revolt.chat all the way to wherever else right wing extremist institutions [mostly evangelicals] nazibuxxx go)
• bcrl 5y ago
  And this is why kernel developers find userland devs to be misguided so much of the time: thread creation is expensive. Thinking that you're saving resources by destroying "unnecessary" threads is not taking into account the system as a whole, especially when you're adding thread creation into what you probably assume is a fast path (waking up a thread in a thread pool). <sigh>
  • TYMorningCoffee 5y ago
    You're right. At the time I did not consider the cost of creating and destroying the thread every ten minutes. Reflecting back on the problem with your comment in mind, the module I wrote could have expected the consumer pass in the thread pool, rather than the module managing it's own pool for something that runs every 10 minutes.
  • pajko 5y ago
    That's why green threads and fibers exist. Green threads implementation of Java has been removed a long time ago, but there's Project Loom: https://developers.redhat.com/blog/2019/06/19/project-loom-lightweight-java-threads# https://developers.redhat.com/blog/2019/06/19/project-loom-l...