Transaction

1d0acbc8f6a7e3460e01092eafc468155b5f938d3b1b47f322bcb66a3c7bc941
Timestamp (utc)
2024-03-24 01:27:27
Fee Paid
0.00000015 BSV
(
0.02071978 BSV
-
0.02071963 BSV
)
Fee Rate
10.12 sat/KB
Version
1
Confirmations
84,750
Size Stats
1,482 B

2 Outputs

Total Output:
0.02071963 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÎ<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=299.msg2420#msg2420">Quote from: asdfman on July 12, 2010, 11:22:54 PM</a></div><div class="quote">from what I saw, there was an error in util.h basically the THREAD_PRIORITY_LOWEST was defined as PRIO_MIN.. the intention was to switch to the "lowest" priority, but in the linux kernel source in resourch.h PRIO_MIN is actually the lowest NUMBER (-20), meaning it actually changed to the HIGHEST priority.. and then after that function is done, it will change priority again (to either 0 or 2, not as bad as -20) but either way it is changing it, so either way no matter what you nice/renice the threads to, it will switch to diff priority levels automatically, with those particular threads that switch priorities never being the most unobtrusive at 19..<br/></div>Yeah, I finally found it as well (I knew I shouldn't have peaked in the code, LOL). I'm going to try manually setting it to hard code 19 and see if that makes a difference after a compile. If so, it might be a more elegant solution that removing the function all together since it appears it's trying to balance out when to use more CPU depending on the system load.</div> text/html
    https://whatsonchain.com/tx/1d0acbc8f6a7e3460e01092eafc468155b5f938d3b1b47f322bcb66a3c7bc941