Transaction

df399d9d006bf22dbe541a03cd515c4a02b06ef237d16d76e40fa01f0dc51b4f
Timestamp (utc)
2024-03-26 21:55:46
Fee Paid
0.00000013 BSV
(
0.00896686 BSV
-
0.00896673 BSV
)
Fee Rate
10.57 sat/KB
Version
1
Confirmations
93,443
Size Stats
1,229 B

2 Outputs

Total Output:
0.00896673 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÐ<div class="post">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/><br/>Its been stated in the latest source code, this min/max is fixed, so if you dl the latest source tree and compile the min/max reversal should be fixed... personally I didnt care of having any of the threads change priority on its own at all, so I just removed the function alltogether..</div> text/html
    https://whatsonchain.com/tx/df399d9d006bf22dbe541a03cd515c4a02b06ef237d16d76e40fa01f0dc51b4f