From 425244ec3d7140626c2fe1180403d0bcd6952db2 Mon Sep 17 00:00:00 2001 From: wakgill <76528604+wakgill@users.noreply.github.com> Date: Sat, 9 Jan 2021 11:08:06 -0600 Subject: [PATCH] Create 196.md --- docs/forum/bitcoin-forum/196.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 docs/forum/bitcoin-forum/196.md diff --git a/docs/forum/bitcoin-forum/196.md b/docs/forum/bitcoin-forum/196.md new file mode 100644 index 0000000..e2530c8 --- /dev/null +++ b/docs/forum/bitcoin-forum/196.md @@ -0,0 +1,25 @@ +--- +layout: forum +title: 'Re: 0.3.1 release candidate, please test' +grand_parent: Forum Posts +parent: Bitcoin Forum +nav_order: 196 +date: 2010-07-15 21:40:34 UTC +original: https://bitcointalk.org/index.php?topic=383.msg3295#msg3295 +--- + +# Re: 0.3.1 release candidate, please test +--- + +
+Re: 0.3.1 release candidate, please test
+July 15, 2010, 09:40:34 PM
+
+Quote from: knightmb on July 15, 2010, 07:37:10 PM
+-------------
+On Windows, the priority of the Coin Generation is still net for normal. If you run BitCoin in Generate Coin mode, then load up something to eat up all the CPU (like CPU hog for example: http://www.microtask.ca/cpuhog.html) you'll see that both BitCoin and CPU hog share the CPU 50/50 instead of CPU Hog taking all the CPU and BitCoin running only on idle/low process. The khash/s is also reduced in half, so further evidence that the threads are not running in a lower than normal prioirty.
+-------------
+
+I was not able to reproduce this.  I have dual-proc, so I ran two memory hogs.  Bitcoin got 0% of CPU according to the task manager.  The khash/sec meter stayed stuck because it couldn't get any CPU to update it.
+
+Do you have dual-proc?  Are you sure you weren't running a single processor hog?