user35755: I just updated my node to 0.12 and its going through its long verification process but I noticed that its not using very much memory/cpu
pi         602 10.5 19.4 352220 184312 ?       Ssl  21:57   1:28 /usr/local/bin/bitcoind -datadir=/home/pi/bitcoinData/.bitcoin -daemon

How can I configure it to optimise all available memory and cpu? I recall a option to bump up the cache from a default of 50 or 100mb but cannot find the option.
I have a 1GB PI 2. Any recommendations on maximum memory to use? I was thinking 900mb if possible.
Thank you for your tips, and any optimizations to make this run best would be great! 

user208: It will by default use all CPU cores available.
However, if the database cache is too small, your node will spend its time fetching and writing database entries from/to disk, rather than verification
You can set the size of the database cache using a bitcoin.conf setting dbcache=N, where N is the number of megabytes of RAM.

35755: <p>I just updated my node to 0.12 and its going through its long verification process but I noticed that its not using very much memory/cpu</p>

<pre><code>pi         602 10.5 19.4 352220 184312 ?       Ssl  21:57   1:28 /usr/local/bin/bitcoind -datadir=/home/pi/bitcoinData/.bitcoin -daemon
</code></pre>

<p>How can I configure it to optimise all available memory and cpu? I recall a option to bump up the cache from a default of 50 or 100mb but cannot find the option.</p>

<p>I have a 1GB PI 2. Any recommendations on maximum memory to use? I was thinking 900mb if possible.</p>

<p>Thank you for your tips, and any optimizations to make this run best would be great! </p>
 208: <p>It will by default use all CPU cores available.</p>

<p>However, if the database cache is too small, your node will spend its time fetching and writing database entries from/to disk, rather than verification</p>

<p>You can set the size of the database cache using a bitcoin.conf setting <code>dbcache=N</code>, where N is the number of megabytes of RAM.</p>
