Bitcoin Wiki - User contributions [en]

P2Pool

2012-03-21T06:36:02Z

NothinG:

[[Image:P2pool_chain.png‎|thumb|350px|right|Visualization of the P2Pool share chain]]
P2Pool is a decentralized [[Bitcoin]] [[Bitcoin Pool|mining pool]] that works by creating a peer-to-peer network of miner nodes.

<blockquote>P2Pool creates a new block chain in which the difficulty is adjusted so a new block is found every 10 seconds. The blocks that get into the P2Pool block chain (called the "share chain") are the same blocks that would get into the Bitcoin block chain, only they have a lower difficulty target. Whenever a peer announces a new share found (new block in the P2Pool block chain), it is received by the other peers, and the other peers verify that this block contains payouts for all the previous miners who found a share (and announced it) that made it into the P2Pool share chain. This continues until some peer finds a block that has a difficulty that meets the Bitcoin network's difficulty target. This peer announces this block to the Bitcoin network and miners who have submitted shares for this block are paid in the generation transaction, proportionally to how many shares they have found in the last while. - Unknown author</blockquote>

Decentralized payout pooling solves the problem of centralized mining pools degrading the decentralization of Bitcoin, avoids the risk of hard to detect theft by pool operators, and has better fundamental resistance to DoS attacks than centralized pools.

Miners are configured to connect to a P2Pool node that can be run locally, alongside the miner. P2Pool users must run a full Bitcoin node which serves the purpose of independently validating transactions and the Bitcoin blockchain. P2Pool also supports merged mining and several alternative blockchains.

P2Pool nodes work on a chain of shares similar to Bitcoin's blockchain. Each node works on a block that includes payouts to the previous shares' owners and the node itself, which can also result in a share if it meets P2Pool's difficulty.

Because of the importance of strengthening Bitcoin's decentralization some Bitcoin supporters donate to P2Pool miners, resulting in returns above 100% of the expected reward.

== Overview ==

P2Pool shares form a "sharechain" with each share referencing the previous share's hash. Each share contains a standard Bitcoin block header, some P2Pool-specific data that is used to compute the generation transaction (total subsidy, payout script of this share, a nonce, the previous share's hash, and the current target for shares), and a Merkle branch linking that generation transaction to the block header's Merkle hash.

The chain continuously regulates its target to keep generation around one share every ten seconds, just as Bitcoin regulates it to generate one block every ten minutes.

Unlike Bitcoin, nodes do not know the entire chain - instead they only hold the last 8640 shares (the last day's worth). In order to prevent an attacker from working on a chain in secret and then releasing it, overriding the existing chain, chains are judged by how much work they have since a point in the past. To ascertain that the work has been done since that point, nodes look at the Bitcoin blocks that the shares reference, establishing a provable timestamp. (If a share points to a block, it was definitely made after that block was made.)

=== Payout logic ===

Each share contains a generation transaction that pays to the previous ''n'' shares, where ''n'' is the number of shares whose total work is equal to 3 times the average work required to solve a block, or 8640, whichever is smaller. Payouts are weighted based on the amount of work each share took to solve, which is proportional to the p2pool difficulty at that time.

The block reward (currently 50BTC) and the transaction fees are combined and apportioned according to these rules:

A subsidy of 0.5% is sent to the node that solved the block in order to discourage not sharing solutions that qualify as a block. (A miner with the aim to harm others could withhold the block, thereby preventing anybody from getting paid. He can NOT redirect the payout to himself.) The remaining 99.5% is distributed evenly to miners based on work done recently.

In the event that a share qualifies as a block, this generation transaction is exposed to the Bitcoin network and takes effect, transferring each node its payout.

=== Stales ===

P2Pool stales don't work the same way as stales on centralized pools. On a centralized pool a stale is work which is too old to be accepted by the pool's Bitcoin node; this kind of stale is very rare in P2Pool because each user runs their own local bitcoind.

On P2Pool stales refer to shares which can't make it into the sharechain. Because the sharechain is 60 times faster than the Bitcoin chain many stales are common and expected. However, because the payout is [[Comparison_of_mining_pools|PPLNS]] only your stale rate relative to other nodes is relevant; the absolute rate is not.

There are two reported kinds of stales in P2Pool: "DEAD ON ARRIVAL" shares and orphan shares. Dead shares were too old by the time they arrived at your local P2Pool. Very high dead rates can indicate miner misconfiguration. Orphan shares are shares which were not extended by the rest of the P2Pool network, because some other miner's share was accepted first. Very high orphan rates may indicate network connectivity problems.

The P2Pool console output shows your relative stale rate compared to other P2Pool miners in the 'Own efficiency' column:
<pre>
2012-01-07 20:57:51.797420 Pool stales: 13% Own: 13±2% Own efficiency: 100±2%
</pre>

When you first start P2Pool claimed efficiency will be low and the error bounds on this estimate will be large, but as it runs the numbers will converge to their correct values.

If your efficiency is unusually low, make sure your network connection isn't overloaded, that your miners support long polling and are not set to work for excessive amounts of time, and that your bitcoind has multiple connections.

== Joining the pool ==

Follow these steps to join the pool:

* Run Bitcoin with the RPC interface enabled: put rpcuser=USER, rpcpassword=LONG_RANDOM_SECRET_VALUE, and server=1 in bitcoin.conf (on separate lines)
**'''Replace LONG_RANDOM_SECRET_VALUE with something long and random like the output of smashing your keyboard for a bit like fju4M78yAj3ds39pak92raK'''. You don't need to be able to remember it. If your RPC port becomes exposed to the internet a thief could steal your bitcoin if they could guess it, or use a brute force attack in order to find it.
** Bitcoin 0.5 or later is required
** It's important that your Bitcoin client be fully synchronized before starting. It's also better if you have the Bitcoin port forwarded
* Download p2pool:
** Windows binary: See http://forum.bitcoin.org/index.php?topic=18313.0
** Source download: https://github.com/forrestv/p2pool/tags
** git: git clone git://github.com/forrestv/p2pool.git
* Run p2pool: (See below for additional options.)
** Windows py2exe: run_p2pool.exe
** Source: python run_p2pool.py
* Run a miner daemon with long polling connecting to 127.0.0.1 (or the IP of the host running p2pool if it isn't on the same computer as the miner) on port 9332 with any username and password
** cgminer -O u:p -o http://127.0.0.1:9332/ --submit-stales

Dependencies if running from source:
* Python 2.6 or higher
* python-argparse for Python 2.6 and lower
* Twisted (Ubuntu package python-twisted)

=== Frequently Asked Questions ===

'''Q:''' "Why does cgminer report so many longpoll events when mining on p2pool? - P4Man" 
'''A:''' "Once every ~10 seconds is normal. That is how often p2pool shares are generated (as opposed to ~10 min for bitcoin blocks) - cabin"

'''Q:''' "Do the 'orphan' and 'dead' shares in P2Pool's status display hurt me?" 
'''A:''' They shouldn't - It's normal for some fraction of everyone's shares to end up orphaned or dead. Because payouts are calculated by counting how many shares you have relative to others, everyone with normal configurations is equally "hurt" by this. However, if you have a large proportion of stales, your payout will be hurt. You can see how well you're doing by looking at P2Pool's "Efficiency" (ex: ''Efficiency: ~110.6% (40-111%)''). If 100% doesn't lie within the [http://en.wikipedia.org/wiki/Confidence_interval confidence interval] at the end, something is probably wrong (with 95% confidence).

'''Q:''' "What do I do if my efficiency is low?" 
'''A:''' Make sure the computers you're running P2Pool and the miner on have enough memory and CPU time. If you have a lot of dead shares or the "Local dead on arrival" number is higher than a few percent, that means that something is wrong with your miner. Check to make sure that it is one of the working versions in the ''Miners'' section on this page. Lower the intensity or raise the FPS of your miner. If you have a lot of orphan shares, something is wrong with P2Pool's P2P connection. Decrease the load on your internet connection or enable QoS (Quality of Service) on your router.

'''Q:''' What is PPLNS? 
'''A:''' Pay-Per-Last-N-Shares is a payout method that is completely resistant to pool hoppers.

'''Q:''' Why am I not getting very many shares?! 
'''A:''' The P2Pool difficulty is hundreds of times higher than on normal pools. It can take time to get a share. P2Pool displays an estimate of how long you have to wait in the console output.

'''Q:''' Why does my miner say it has found a lot of shares but p2pool say I have only found a few?! 
'''A:''' The real P2Pool difficulty is hundreds of times higher than on normal pools, but p2pool essentially lies to your miner and tells it to work on relatively easy shares so that it submits shares every few seconds instead of every few hours. P2Pool then ignores any submitted shares that don't match the real share difficulty. By doing this, P2Pool can more accurately report your local hash rate and you can see if you are having problems with too many stale shares quickly

'''Q:''' Why am I getting so many rejects? 
'''A:''' You're using an incompatible miner. See the miners section here, increase your FPS on the miner, decrease the intensity, upgrade your miner, or try a different miner.

'''Q:''' What stops the pool operator or the block finder from stealing a block? 
'''A:''' A block solution is only worth anything because its hash matches Bitcoin's target. Altering anything within the block will change its hash and make it worthless.

'''Q:''' Why does it say "Generated?" I want to spend my coins now! 
'''A:''' P2Pool includes payouts in generation transactions, which must mature (taking 120 blocks or 20 hours) before they can be spent. The reason for this is that a block could be orphaned, which would make its payout invalid and could reverse transactions.

'''Q:''' Do I get paid transaction fees? 
'''A:''' Yes. They are split among P2Pool miners.

'''Q:''' What are these payments I'm getting that aren't generated? 
'''A:''' These are subsidies that people who support the idea of P2Pool send to miners.

'''Q:''' Cool Subsidies sound like an awesome idea! How do I send some BTC to these awesome miners? 
'''A:''' See end of this page.

'''Q:''' Do I really need the WHOLE blockchain? 
'''A:''' Yes. Your node needs to be able to independently make decisions about what transactions to mine.

'''Q:''' How do merged mining payments work? 
'''A:''' Merged mining is handled entirely by namecoind, so you're solo mining and payouts will go into namecoind's wallet.

=== Miners ===

This is all for the latest p2pool version, as it includes several new workarounds.

With all miners, using a HIGH FPS target (100?) or a LOW intensity (8 for cgminer?) helps a lot with reducing stales.

* cgminer works perfectly without any extra options. However, using multiple pools might cause problems, because long polling is only done for one pool.
* ufasoft works perfectly.
* DiabloMiner works fine after commit 3b731b9.
* Phoenix works fine after commit a658ef2.
* Poclbm works fine after commit 5e994e7.

P2Pool uses higher difficulty shares than most centralized pools, so you'll see fewer shares reported. This is normal and doesn't reduce your payments. It's also normal to see longpoll messages once per every ten seconds on average.

=== Useful features ===

* If upgrading P2Pool or changing its configuration, you can start another instance of P2Pool in parallel with the first. It will start normally, but realize that the worker and P2P listening ports are busy and keep trying to bind to them in the background. Thus, you can do almost-completely-seemless upgrades of P2Pool.
* If you run multiple P2Pool nodes or have trusted friends that run P2Pool, you can use ''-n'' to establish a constant extra P2P connection to them.
* You can make P2Pool use a configuration file by running run_p2pool.py @FILENAME, with FILENAME being the path to a file containing the command-line arguments (newlines are ignored) Example:
<pre>
--net litecoin
-n 1.2.3.4
</pre>
* Setting the username of your miner connecting to P2Pool to a Bitcoin address will make it mine to that address instead of the one requested from bitcoind or set by -a

=== Web interface ===

Lots of data and useful tools are available at http://127.0.0.1:9332/something:
* /graphs - RRD graphs of past hash rates for pool and local miners. Look for "VIP password" in P2Pool's output when it starts and use that for your miners to get graphs for individual miners.
* /rate
* /users
* /fee
* /current_payouts
* /patron_sendmany - Gives sendmany outputs for fair donations to P2Pool
* /global_stats
* /local_stats
* /peer_addresses
* /payout_addr
* /recent_blocks
* /uptime
* /chain_img - Visualization of sharechain
* /web/log - Some different stats collected over the last day

=== Included README ===
<pre>
Requirements:
Generic:
Bitcoin >=0.5.0 or Litecoin
Python
Twisted
python-argparse (for Python <=2.6)

Linux:
sudo apt-get install python-zope.interface python-twisted python-twisted-web
sudo apt-get install python-argparse # if on Python 2.6 or older

Windows:
Install Python 2.7: http://www.python.org/getit/
Install Twisted: http://twistedmatrix.com/trac/wiki/Downloads
Install Zope.Interface: http://pypi.python.org/pypi/zope.interface/3.8.0
Unzip the files into C:\Python27\Lib\site-packages

Running P2Pool:
To use P2Pool, you must be running your own local bitcoind. For standard
configurations, using P2Pool should be as simple as:

python run_p2pool.py

Then run your miner program, connecting to 127.0.0.1 on port 9332 with any
username and password.

If you are behind a NAT, you should enable TCP port forwarding on your
router. Forward port 9333 to the host running P2Pool.

Run "python run_p2pool.py --help" for additional options.

Notes for Litecoin:
Requirements:
In order to run P2Pool with the Litecoin network, you would need to build and install the
ltc_scrypt module that includes the scrypt proof of work code that Litecoin uses for hashes.

Linux:
cd litecoin_scrypt
sudo python setup.py install

Windows:
Install MinGW: http://www.mingw.org/wiki/Getting_Started
Install Python 2.7: http://www.python.org/getit/

cd litecoin_scrypt
C:\Python27\python.exe setup.py build --compile=mingw32 install

If you run into an error with unrecognized command line option '-mno-cygwin', see this:
http://stackoverflow.com/questions/6034390/compiling-with-cython-and-mingw-produces-gcc-error-unrecognized-command-line-o

Running P2Pool:
Run P2Pool with the "--net litecoin" option.
Run your miner program, connecting to 127.0.0.1 on port 9327.
Forward port 9338 to the host running P2Pool.

Litecoin's use of ports 9332 and 9332 conflicts with P2Pool running on
the Bitcoin network. To avoid problems, add these lines to litecoin.conf
and restart litecoind:
rpcport=10332
port=10333
</pre>

=== Option Reference ===
<pre>
usage: run_p2pool.py [-h] [--version] [--net {bitcoin, litecoin}] [--testnet]
[--debug] [-a ADDRESS] [--datadir DATADIR]
[--logfile LOGFILE] [--merged MERGED_URLS]
[--merged-url MERGED_URL]
[--merged-userpass MERGED_USERPASS]
[--give-author DONATION_PERCENTAGE] [--irc-announce]
[--p2pool-port PORT] [-n ADDR[:PORT]] [--disable-upnp]
[-w PORT] [-f FEE_PERCENTAGE]
[--bitcoind-address BITCOIND_ADDRESS]
[--bitcoind-rpc-port BITCOIND_RPC_PORT]
[--bitcoind-p2p-port BITCOIND_P2P_PORT]
[BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]

p2pool (version 28a1948)

optional arguments:
-h, --help show this help message and exit
--version show program's version number and exit
--net {bitcoin, litecoin}
use specified network (default: bitcoin)
--testnet use the network's testnet
--debug enable debugging mode
-a ADDRESS, --address ADDRESS
generate payouts to this address (default: <address
requested from bitcoind>)
--datadir DATADIR store data in this directory (default: <directory
run_p2pool.py is in>/data)
--logfile LOGFILE log to this file (default: data/<NET>/log)
--merged MERGED_URLS call getauxblock on this url to get work for merged
mining (example:
http://ncuser:ncpass@127.0.0.1:10332/)
--merged-url MERGED_URL
DEPRECATED, use --merged
--merged-userpass MERGED_USERPASS
DEPRECATED, use --merged
--give-author DONATION_PERCENTAGE
donate this percentage of work to author of p2pool
(default: 0.5)
--irc-announce announce any blocks found on
irc://irc.freenode.net/#p2pool
--disable-upnp don't attempt to use UPnP to forward p2pool's P2P port
from the Internet to this computer

p2pool interface:
--p2pool-port PORT use port PORT to listen for connections (forward this
port from your router!) (default: bitcoin:9333,
litecoin:9338)
-n ADDR[:PORT], --p2pool-node ADDR[:PORT]
connect to existing p2pool node at ADDR listening on
port PORT (defaults to default p2pool P2P port) in
addition to builtin addresses

worker interface:
-w PORT, --worker-port PORT
listen on PORT for RPC connections from miners
(default: bitcoin:9332, litecoin:9327)
-f FEE_PERCENTAGE, --fee FEE_PERCENTAGE
charge workers mining to their own bitcoin address (by
setting their miner's username to a bitcoin address)
this percentage fee to mine on your p2pool instance.
Amount displayed at http://127.0.0.1:WORKER_PORT/fee
(default: 0)

bitcoind interface:
--bitcoind-address BITCOIND_ADDRESS
connect to this address (default: 127.0.0.1)
--bitcoind-rpc-port BITCOIND_RPC_PORT
connect to JSON-RPC interface at this port (default:
bitcoin:8332, litecoin:9332 <read from bitcoin.conf if
password not provided>)
--bitcoind-p2p-port BITCOIND_P2P_PORT
connect to P2P interface at this port (default:
bitcoin:8333, litecoin:9333 <read from bitcoin.conf if
password not provided>)
BITCOIND_RPCUSERPASS bitcoind RPC interface username, then password, space-
separated (only one being provided will cause the
username to default to being empty, and none will
cause P2Pool to read them from bitcoin.conf)
</pre>

== Protocol description ==

P2Pool's protocol mirrors Bitcoin's P2P protocol in many ways. It uses the same framing (prefix, command, length, checksum, payload) and similar commands:

* '''version''' - sent to establish a connection - contains (''version'', ''services'', ''addr_to'', ''addr_from'', ''nonce'', ''sub_version'', ''mode'', ''best_share_hash'')
* '''setmode''' - sent to update the ''mode'' sent in the '''version''' message - contains (''mode'')
* '''ping''' - sent to keep connection alive - contains ()
* '''addrme''' - request that the receiving node send out an addr for the sending node - contains (''port'')
* '''addrs''' - broadcast list of nodes' addresses - contains (''addrs'')
* '''getaddrs''' - request that the receiving node send ''count'' addrs - contains (''count'')
* '''getshares''' - request that the receiving node send the shares referenced by ''hashes'' and ''parents'' of their parents, stopping at any share referenced by ''stops'' - contains (''hashes'', ''parents'', ''stops'')
* '''shares''' - broadcast message of the contents of shares - contains (''shares'')

==History==

This project was announced on June 17, 2011 by Forrest Voight<ref>[https://forum.bitcoin.org/index.php?topic=18313.0 p2pool: Decentralized, DoS-resistant, Hop-Proof - Now active on mainnet!]</ref>.

The began testing against mainnet in mid-July, 2011. The pool was reviewed on a [[Bitcoin Miner]] post on July 26, 2011<ref>[http://www.bitcoinminer.com/post/8101660461 P2Pool Decentralized Pool Nearly Ready For Prime-Time]</ref>.

The software author's address for donations can be found in the signature section of his [http://forum.bitcoin.org/index.php?action=profile;u=6447 forum profile].

==Donating to P2Pool miners==
In order to encourage people to mine to P2Pool you can donate to the recent miners in proportion using a sendmany:

For example, a bash script to donate 10 btc is:
<pre>
~/src/bitcoin/src/bitcoind sendmany "" "$(GET http://forre.st:9332/patron_sendmany/10)"
</pre>

You can replace "" with "accountname" if you want to pay from some specific bitcoind account, and you can replace forre.st with 127.0.0.1 if you're running a P2Pool node locally, so you don't have to trust that the URL gives accurate figures.

Note that the amount you donate will be allocated to recent miners in proportion to the amount of work they've done in the last 24 hours or so, but all the miner whose shares of the donated amount are less than 0.01 BTC will have their shares combined into a single amount which is awarded to one of them at random, with the chance of winning this 'lottery' weighted by the miner's recent amount of work done. You can change this 0.01 BTC threshold like this, for example, which says to pay 10 BTC, but to share it amongst more miners that the default, cutting off at 0.001 BTC instead of at 0.01 BTC.
<pre>
~/src/bitcoin/src/bitcoind sendmany "" "$(GET http://forre.st:9332/patron_sendmany/10/0.001)"
</pre>

If you decide to donate you should announce it on the forums so that your donations provide the most incentive possible.

==See Also==

* [[Comparison of mining pools]]
* [[Pooled Mining]]

==External Links==

* [http://forum.bitcoin.org/index.php?topic=18313.0 P2Pool forum]
* [https://github.com/forrestv/p2pool p2pool] project on GitHub
* {{Freenode IRC|p2pool}} discussion and support
* [http://p2pool.info/ p2pool.info] stats page
* [http://nodes.p2pmine.com nodes.p2pmine.com] Public list of P2Pool BTC/LTC nodes.

==References==
<references />

[[Category:Pool Operators]]

Fallback Nodes

2011-08-14T21:14:18Z

NothinG: /* IPv4 Nodes */

This is a list of nodes which are considered reliable. Nodes from this list which are down for more than 24 hours will be automatically removed and status of each node is displayed and updated every hour by [[User:WikiBot|WikiBot]].

== How to use this list ==

=== Connect to nodes ===

You can connect to these nodes with the ''-addnode=ip'' switch instead of the usual node harvesting process (through IRC or via the embedded nodelist). You can connect to more than one node by using ''-addnode=ip'' more than once. It is usually a good idea to connect to more than one of these nodes.

==== Nodes without a fixed ip ====

If the node IP is not fixed (see "Fixed" column), you will have to resolve the node's name (first column) each time the IP changes. Some nodes may have their ip change once a day, some others once a month, and some others may stay on the same IP for years. Still, as long as the IP is not fixed, there is no guarantee it will stay the same.

In order to enable hostname lookups for the ''-addnode'' and ''-connect'' parameters, you must additionally provide the ''-dns'' parameter. Example:
bitcoind -dns -addnode=bitcoin.es

Versions prior to 0.3.22 do not support hostnames to the ''-addnode'' parameter, so you must do the resolving part for it. For example on linux:
bitcoind -addnode=$(dig +short bitcoin.es)

=== IP Transactions ===

You can also send [[IP Transactions]] to these nodes. If you include your bitcoin address in the "message" field, you may have your coins back.

=== Tor network ===

To use tor .onion addresses, you need to map virtual ips via the ''torrc'' file:

mapaddress 192.0.2.2 ijzt2eeizty3p5xe.onion
mapaddress 192.0.2.3 j43z65b6r2usg3vk.onion
mapaddress 192.0.2.4 pvuif6nonbhj3o3r.onion

Once you have configured and restarted tor, 192.0.2.2 will connect to ijzt2eeizty3p5xe.onion when accessed through the Tor proxy (and likewise for the other IPs/onions). You can then run Bitcoin with -addnode=192.0.2.2, or even send bitcoins to that IP address. You can use any arbitrary IP addresses with MapAddress, though some of the common non-routable ranges (10.*, 192.168.*) will not work due to a Bitcoin bug. 192.0.2.1-192.0.2.255 is the recommended range because it is both non-routable and compatible with Bitcoin.

== Nodes list ==

=== IPv4 Nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! IP !! Fixed !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-

| 204.9.55.71 || toasty || 204.9.55.71 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.25}} || 2011-08-14 21:00:04 || ?
|-
| 50.23.217.19 || Senseless || 50.23.217.19 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-08-14 21:00:04 || No
|-
| 66.158.72.2 || imsaguy || 66.158.72.2 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-08-14 21:00:04 || ?
|-
| 93.186.32.118 || rfcpool.com || 93.186.32.118 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-08-14 21:00:04 || ?
|-
| 98.143.152.14 || osmosis || 98.143.152.14 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-08-14 21:00:05 || ?
|-
| 173.224.125.222 || MagicalTux [US] || 173.224.125.222 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-08-14 21:00:10 || ?
|-
| bitcoin.es || neutrino || 188.165.138.165 || {{Table Value Yes}} || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-08-14 21:00:10 || ?
|-
| btcnode.novit.ro || ovidiusoft - novit.ro || 93.187.142.114 || || {{Fallback Nodes/Node Up|version=0.3.24}} || 2011-08-14 21:00:10 || Yes
|-
| 74.57.236.239 || ? || 74.57.236.239 || {{Table Value Yes}} || {{Fallback Nodes/Node Old|version=0.3.0}} || 2011-08-14 21:00:10 || ?
|-
| 216.135.68.67 || NothinG

|}

=== Tor nodes ===

{|class="wikitable sortable"
! Hostname !! Owner !! Status !! Last Seen (GMT) !! Accepts IP transactions
|-
| ijzt2eeizty3p5xe.onion || ? || ? || 2011-02-11 || Yes
|-
| j43z65b6r2usg3vk.onion || Dybbuk || ? || 2011-02-11 || Yes
|-
| pvuif6nonbhj3o3r.onion || ? || ? || 2011-02-11 || Yes
|-
| c5qvugpewwyyy5oz.onion || ? || ? || 2011-02-11 || Yes
|-
| vso3r6cmjoomhhgg.onion || echelon || ? || 2011-02-11 || Yes
|-
| bitcoinbudtoeks7.onion || ? || ? || 2011-02-11 || ?
|-
| iy6ni3wkqazp4ytu.onion || ? || ? || 2011-02-11 || ?
|-
| h4kklwodpcmo6cbq.onion || ? || ? || 2011-02-11 || ?
|-
| vv6kcfscuntybrzm.onion || ? || ? || 2011-02-11 || ?
|-
| nlnsivjku4x4lu5n.onion || ? || ? || 2011-02-11 || ?
|-
| xqzfakpeuvrobvpj.onion || ? || ? || 2010-11-13 || No
|-
| 4lmduyac3svgrrav.onion || ? || ? || 2011-02-11 || No
|-
| usasx4urod3yj4az.onion || ? || ? || 2011-02-11 || No
|}

== Adding a node ==

Before adding yourself as a fallback node, you should be sure your node will stay online for a long time. If a node is offline for more than 24 hours it will be removed from the list. To accept IP transactions you will have to add the ''-allowreceivebyip'' flag to your command line parameters.

To add a node in this list, you just need the ip/hostname and your name, the other fields will be filled automatically. Insert the following lines before the <tt>END NODELIST</tt> line:

<nowiki>|-
| ip || your name</nowiki>

Please note that a bot will connect to your node every hour to check its status and version.

Mining hardware comparison

2011-06-11T09:46:02Z

NothinG: /* Nvidia */

Below are some statistics about the mining performance of various hardware used in a [[mining rig]].

The table shows (mostly) stock clock numbers. 10-20% performance improvement can be achieved via overclocking.

'''Note:''' Clock refers to the Shader clock only with nVidia cards (not Core or Memory). With AMD card the shader clock is not separate, but is part of the GPU clock.

W = Watt (maximum power consumption)

SP = Stream processors (Shader Units)

==Graphics cards==

===AMD (ATI)===
To get the maximum performance use the 2.1 release of the ATI Stream SDK. 2.2 wastes CPU time, and 2.3/2.4 drop mining performance by 5-10% unless using the Phoenix phatk kernel.

{| class="wikitable sortable"
|-
! Model !! Mhash/s !! Mhash/J !! W !! Clock !! SP !! SDK !! Slot !! Miner !! Notes
|-
| 3XXX || || || || || || || || || OpenCL Not Supported
|-
| 42XX || || || || || || || || || OpenCL Not Supported (intergrated/mobile GPU)
|-
| 4350 || 6.93 || 0.346 || 20 || 575 || 80 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors
|-
| 4550 || 7.23 || 0.289 || 25 || 600 || 80 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors
|-
| 4570M || 8.02 || 0.297 || 27 || 680 || 80 || || PCI-E 2.0 x16 || Diablo/Windows7 || -w 64, SDK 2.4, Cat 11.4. Model: Sony Vaio NW
|-
| 4570M || 9.6 || 0.300 || 32 || 825 || 80 || || PCI-E 2.0 x16 || Diablo/Windows7 || -w 64, SDK 2.4, Cat 11.4. Model: Sony Vaio NW. O/C core 680->825. U/C memory 800->500.
|-
| 4650 || 31.33 || 0.653 || 48 || 650 || 320 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors
|-
| 4670 || 36.14 || 0.613 || 59 || 750 || 320 || || PCI-E 2.0 x16 || poclbm || -w 32, don't use vectors
|-
| 4670 || 40.11 || 0.679 || 59 || 800 || 320 || || AGP x8 || poclbm/Ubuntu 10.10 w/ H == 0 mod || -w 32 -f 0, don't use vectors [http://www.bitcoin.org/smf/index.php?topic=1334.msg85236#msg85236 source]
|-
| 4730 || 72.29 || 0.657 || 110 || 750 || 640 || || PCI-E 2.0 x16 || ||
|-
| 4770 || 72.29 || 0.904 || 80 || 750 || 640 || || PCI-E 2.0 x16 || ||
|-
| 4830 || 55.42 || 0.583 || 95 || 575 || 640 || || PCI-E 2.0 x16 || ||
|-
| 4830 || 66.12 || 0.503 || 105 || 700 || 1005 || || PCI-E 2.0 x16 || ||
|-
| 4850 || 75.30 || 0.685 || 110 || 625 || 800 || || PCI-E 2.0 x16 || ||
|-
| 4850 || 84.3 || 0.766 || 110 || 725 || 300 || || PCI-E 2.0 x16 || || -w64 fan at 70% temp 73C, stock voltage -gui miner
|-
| 4850 || 90.1 || 0.819 || 110 || 800 || 500 || || PCI-E 2.0 x16 || guiminer || -f 30; Tried phoenix and phatk, got same max
|-
| 4850 || 101 ||0.918 || 110 || 817 || 500 || 2.1 || PCI-E 2.0 x16 || guiminer || -f 0, core 817mhz(default 625)@1.123v , mem downclock to 500mhz (default 993) [http://www.smpake.com/?p=6 source]
|-
| 4860 || 67.47 || 0.519 || 130 || 700 || 640 || || PCI-E 2.0 x16 || ||
|-
| 4870 || 92.84 || 0.6189333... (?) || 150 (?) || 830 || 800 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.48 || -k poclbm AGGRESSION=5 (Windows 7 64-Bit, GPU OC 750->830MHz, VRAM UC 900->450MHz, BIOS modded)
|-
| 4870 || 104.6 || 0.872 || 120 || 830 || 800 || 2.1 || PCI-E 2.0 x16 || poclbm || -w 256 -f 1, Windows 7 64-Bit, GPU Core OC to 830 MHz, GPU Memory UC to 190 MHz (saves 30 Watt at outlet)
|-
| 4870 || 90.36 || 0.602 || 150 || 750 || 800 || 2.1 || PCI-E 2.0 x16 || clmine ||
|-
| 4870 || 78 || 0.520 || 150 || || || || PCI-E 2.0 x16 || m0mchil's OpenCL/Vista 64bit || [http://www.bitcoin.org/smf/index.php?topic=1628.msg25069#msg25069 source]
|-
| 4890 Sapphire fab. OC || 97.1 || 0.511 || 190 || 870 || 1050 || 2.4 || PCI-E 2.0 x16 || GUIMiner v2011-01-21 Solo settings || No flags options helped. Close all browsers and do full restart of GUIMiner and then Bitcoin via GUIMiner server starter or the browsers GPU accl. will limit to 56~ ish Mhash/s - I can now start browser without slowdowns
|-
| 4890 || 102.41 || 0.539 || 190 || 850 || 800 || || PCI-E 2.0 x16 || ||
|-
| 4890 || 108.3 || || 190 || 975 || 800 || || PCI-E 2.0 x16 || ||
|-
| 4850X2 || 150.60 || 0.602 || 250 || 625 || 1600 || || PCI-E 2.0 x16 || ||
|-
| 4870X2 || 180.72 || 0.632 || 286 || 750 || 1600 || || PCI-E 2.0 x16 || ||
|-
| 4870X2 || 180.6 || 0.632 || 286 || 800 || 1600 || || PCI-E 2.0 x16 || ||
|-
| 5450 || 11.99 || 0.631 || 19 || 650 || 80 || || PCI-E 2.1 x16 || ||
|-
| 5450 || 13.74 || - || - || 700 || - || || PCI-E 2.1 x16 || poclbm/Linuxcoin v0.2 ||-v -w128 tried several options, seems to work best.
|-
| 5450 || 14.12 || - || - || 700 || - || || PCI-E 2.1 x16 || Phoenix/Linuxcoin v0.2 ||Flags: "DEVICE=0 VECTORS AGGRESSION=4 -v FASTLOOP BFI_INT WORKSIZE=64" Kernel: "phatk"
|-
| 5550 || 40.59 || 1.041 || 39 || 550 || 320 || || PCI-E 2.1 x16 || ||
|-
|style="background:#FFFFEF;"| 5570 || 59.96 || 1.538 || 39 || 650 || 400 || || PCI-E 2.1 x16 || ||
|-
|style="background:#FFFFEF;"| 5570 || 64 || 1.641 || 39 || 650 || || || PCI-E 2.1 x16 || m0mchil's OpenCL/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
|style="background:#FFFFEF;"| 5570 || 62 || 1.59 || 39 || 650 || 400 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.48 OpenCL/Linux x86_64 || -k phatk DEVICE=0 VECTORS AGGRESSION=4 -v FASTLOOP BFI_INT WORKSIZE=64
|-
|style="background:#FFFFEF;"| 5570 || 73 || 1.872 || 39 || 700 || 400 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.48 OpenCL/Linux x86_64 || -k phatk DEVICE=0 VECTORS AGGRESSION=4 -v FASTLOOP BFI_INT WORKSIZE=64
|-
|style="background:#FFFFEF;"| 5570 || 102 || || <75 || 950 || 400 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.48 OpenCL/Windows 7 x86 (no Aero) || -k phatk DEVICE=0 VECTORS AGGRESSION=7 -v FASTLOOP BFI_INT WORKSIZE=256 (Reference Sapphire card, 2 additional 120mm coolers, temperature is 79-82C)
|-
| 5650 || 48 || 1.37 || 35 ? || || || || PCI-E 2.1 x16 || m0mchil's OpenCL/Win7-64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26292#msg26292 source] [http://www.notebookcheck.net/ATI-Mobility-Radeon-HD-5650.23697.0.html source] -- not TDP but load
|-
| 5670 || 71.49 || 1.117 || 64 || 775 || 400 || || PCI-E 2.1 x16 || ||
|-
|style="background:#EEFFEE;"| 5670 || 72 || 1.64 || 44 || 850 || || || PCI-E 2.0 x16 || poclbm-mod (Win7-64) || Sapphire 100287VGAL card is low power
|-
| 5670 || 85 || || || 900 || 400 || || PCI-E 2.1 x16 || poclbm || -v -f 0 -w 128
|-
| 5750 || 116.24 || 1.352 || 86 || 700 || 720 || || PCI-E 2.1 x16 || ||
|-
| 5750 || 137 || || || 710 || || || PCI-E 1.1 x16 || poclbm || -v -f 0 -w 128 using stock memory and GPU clocks
|-
| 5750 || 146.4 || || || 775 || || || PCI-E 2.0 x16 || GUIMiner v2011-05-21 || -v -w128, AMD Catalyst overclock (775MHz GPU / 1225 MHz Memory)
|-
| 5750 || 154.56 || 1.45 || 106 || 830 || 720 || || PCI-E 2.1 x16 || ||-v -w128 -f20 underclocked memory clocks from 1150MHz to 300MHz
|-
| 5750 || 170 || || || 870 || || || PCI-E 1.1 x16 || poclbm || -v -f 0 -w 128 patched BIOS to underclock memory to 300MHz
|-
| 5750 || 173 || || || 875 || || || PCI-E 1.1 x16 || phoenix || 875/300 w/MSI Afterburner, BFI_INT VECTORS AGGRESSION=12 FASTLOOP=FALSE -k phatk
|-
|style="background:#FFFFEF;"| 5770 || 156.83 || 1.452 || 108 || 850 || 800 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
|style="background:#FFFFEF;"| 5770 || 180 || 1.406 || 128[*] || 950 || 800 || 2.4RC1 || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 30 (*Overclocked wattage calculated [http://bakkap.free.fr/Misc/wCalc.html here] )
|-
|style="background:#FFFFEF;"| 5770 || 205.58 || || || 935 || 300 || 2.1 || PCI-E 2.1 x16 || poclbm 2011-04-28 || -v -w 256
|-
|style="background:#FFFFEF;"| 5770 || 210.7 || || 108+ || 950 || 800 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / win7x86 || mem underclocked 309 mhz, -k phatk DEVICE=0 VECTORS BFI_INT FASTLOOP=false AGGRESSION=12
|-
|style="background:#FFFFEF;"| 5770 || 218.35 || || || 1000 || 1401 || 2.1 || PCI-E 2.0 x16 || DiabloMiner || -w 128 -v 2 (Overclocked to 1Ghz core with 1.2 voltage and Scythe Setsugen 2 cooling system)
|-
|style="background:#FFFFEF;"| 5770 || 223 || || 100+ || 1050 || 300 || 2.4 || PCI-E 2.1 x16 || guiminer || -v -w256 [http://www.smpake.com/?p=59 source]
|-
|style="background:#FFFFEF;"| 5770 || 233 || || 100+ || 1050 || 300 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 || VECTORS BFI_INT FASTLOOP=false AGGRESSION=12 -k phatk WORKSIZE=256 [http://www.smpake.com/?p=59 source]
|-
|style="background:#FFFDDD;"| 5830 || 244 || 1.52 || 179 || 800 || 1000 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.48 OpenCL/Linux x86_64 || -k phatk DEVICE=1 VECTORS AGGRESSION=6 -v FASTLOOP WORKSIZE=128 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 267 || || || 875 || 1000 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.48 OpenCL/Linux x86_64 || -k phatk DEVICE=1 VECTORS AGGRESSION=6 -v FASTLOOP WORKSIZE=128 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 245 || 1.28 || 192 || 880 || 900 || 2.4 || PCI-E 2.1 x16 || poclbm (guiminer) || -v -w 256
|-
|style="background:#FFFDDD;"| 5830 || 248 || 1.29 || 192 || 880 || 500 || 2.4 || PCI-E 2.1 x16 || phoenix 1.46 || -k poclbm VECTORS BFI_INT AGGRESSION=11
|-
|style="background:#FFFDDD;"| 5830 || 256 || || || 900 || 300 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 || -k poclbm VECTORS BFI_INT AGGRESSION=7
|-
|style="background:#FFFDDD;"| 5830 || 270 || || 175 || 900 || 1000 || 2.1 || PCI-E 2.1 x16 || poclbm (guiminer) Win7x64 || -v -w 256, XFX stock w/ v2.4 SDK = 230Mh/s, v2.1 SDK = +10Mh/s, overclocking core clock by 100 = +30Mh/s.
|-
|style="background:#FFFDDD;"| 5830 || 272 || 1.52 || 179 || 875 || || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / LinuxCoin || 275Mhz Memory clock, 1.125 V (from 1.163), VECTORS AGGRESSION=12 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 285 || || || 960 || || 2.4 || PCI-E 2.1 x16 || phoenix 1.47 / poclbm / Win7 64 || VECTORS BFI_INT FASTLOOP=false AGGRESSION=12
|-
|style="background:#FFFDDD;"| 5830 || 290 || || || 996 || || 2.4 || PCI-E 2.1 x16 || phoenix 1.4 / poclbm / Win7 64 || VECTORS AGGRESSION=12 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 300 || || || 970 || 1120 || 2.1 || PCI-E x16 || phoenix 1.48 / phatk / Win7 64 || 300Mhz memory clock BFI_INT AGGRESSION=12 FASTLOOP=false WORKSIZE=256
|-
|style="background:#FFFDDD;"| 5830 || 305 || || || 984 || || 2.4 || PCI-E 2.1 x16 || phoenix 1.4 / phatk / Win7 32 || 400Mhz Memory clock, VECTORS AGGRESSION=12 BFI_INT FASTLOOP=false
|-
|style="background:#FFFDDD;"| 5830 || 307 || || || 996 || || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / Win7 64 || VECTORS AGGRESSION=12 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 308 || || || 990 || 375 || 2.1 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / Win7 32 ||@ stock voltage VECTORS AGGRESSION=11 -v FASTLOOP=false BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 316.35 || || || 1015 || 375 || 2.1 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / Win7 32 ||@ stock voltage VECTORS AGGRESSION=12 -v FASTLOOP=false BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 318 || || || 1030 || || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / Win7 64 || 385Mhz Memory, VECTORS AGGRESSION=9 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 || 319 || || || 1030 || || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 / phatk / Xp 64 || 1.2v 355Mhz Memory, VECTORS AGGRESSION=12 BFI_INT
|-
|style="background:#FFFDDD;"| 5830 black || 310 || || || 990 || 300 || 2.4 || PCI-E 2.1 x8 || LinuxCoin 0.2b, phoenix/phatk || (XFX Brand) -k phatk VECTORS BFI_INT WORKSIZE=256 AGGRESSION=11 FASTLOOPS=false
|-
|style="background:#EFEFFF;"| 5850 || 240.77 || 1.595 || 151 || 725 || 1440 || || PCI-E 2.1 x16 || ||
|-
|style="background:#EFEFFF;"| 5850 || 250.26 || 1.657 || 151 || 725 || 1440 || || PCI-E 2.1 x16 || opencl client || [http://www.bitcoin.org/smf/index.php?topic=1628.msg29471#msg29471 source]
|-
|style="background:#EFEFFF;"| 5850 || 252 || 1.575 || 160 || 765 || 1440 || 2.3 || PCI-E 2.1 x16 || poclbm 2011-01-25 ||
|-
|style="background:#EFEFFF;"| 5850 || 255.3 || 1.593 || 160 || 765 || 1440 || 2.2 || PCI-E 2.1 x16 || poclbm 2011-01-25 ||
|-
|style="background:#EFEFFF;"| 5850 || 264 || 1.748 || 151 || 725 || 1440 || 2.4 || PCI-E 1.0 x8 || guiminer-20110501 || -v -w128
|-
|style="background:#EFEFFF;"| 5850 || 280 || 1.75 || 160 || 765 || 1440 || 2.2 || PCI-E 2.1 x16 || Phoenix 1.3 || with BFI_INT
|-
|style="background:#EFEFFF;"| 5850 || 292 || 1.825 || 160 || 765 || 1440 || 2.1 || PCI-E 2.1 x16 || poclbm 2011-04-28 -v -f 1 ||
|-
|style="background:#EFEFFF;"| 5850 || 298 || 1.8620 || 160 || 765 || 1440 || 2.1 || PCI-E 2.1 x16 || poclbm 2011-04-28 -v -f 1 -w 64 ||
|-
|style="background:#EFEFFF;"| 5850 || 300 || 1.5460 || 194 || 925 (OC) || 1440 || || PCI-E 2.1 x16 || m0mchil's OpenCL || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
|style="background:#EFEFFF;"| 5850 || 314 || 1.8362 || 171 || 820 (OC) || 1440 || 2.4 || PCI-E 1.0 x8 || poclbm || -v -w128
|-
|style="background:#EFEFFF;"| 5850 || 330 || || || 850 @ Stock voltage || 1440 || 2.1 || PCI-E 2.0 x16 || phoenix || EAH5850, miner arguments: -k poclbm DEVICE=1 VECTORS AGGRESSION=8 WORKSIZE=128 BFI_INT FASTLOOP=false
|-
|style="background:#EFEFFF;"| 5850 || 335 || 1.8611 || 180 || 890 (OC) || 1440 || 2.4 || PCI-E 2.0 x8 || poclbm || -v -w128, Memory downclocked to 300Mhz
|-
|style="background:#EFEFFF;"| 5850 || 344 || 1.8594 || 185 || 890 (OC) || 1440 || || PCI-E 2.0 x16 || phoenix ||
|-
|style="background:#EFEFFF;"| 5850 || 354 || || || 900 (OC) || 1440 || || PCI-E 2.0 x16 || diablo -v 2 -w 128 || Ubuntu 11.04 64-bit [http://forum.bitcoin.org/index.php?topic=9239.0 Headless], 2.1 sdk, catalyst 11.5, memory downclocked to 300mhz, stock voltage. flashed with atiflash [http://www.youtube.com/watch?v=U9AxNmOy6_0 video]
|-
|style="background:#EFEFFF;"| 5850 || 365 || || || 920 || 1440 || 2.1 || PCI-E x16 || phoenix 1.48 / phatk / Win7 64 || 300Mhz memory clock VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false WORKSIZE=256
|-
|style="background:#EFEFFF;"| 5850 || 382 || 1.8454 || 207 || 995 (OC) || 1440 || || PCI-E 2.0 x8 || phoenix || OC 1.177v on core
|-
| 5870M || 152.5 || || || 750 (OC) || 1000 || 2.1 || PCI-E 2.1 x16 || gui-miner (win-7) ||
|-
|style="background:#EFFFEF;"| 5870 || 313.65 || 1.668 || 188 || 850 || 1600 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
|style="background:#EFFFEF;"| 5870 || 313 || 1.665 || 188 || 900? || 1600 || 2.3 || PCI-E 2.1 x16 || Diablo/Linux ||
|-
|style="background:#EFFFEF;"| 5870 || 343 || 1.824 || 188 || 900? || 1600 || 2.1 || PCI-E 2.1 x16 || Diablo/Linux ||
|-
|style="background:#EFFFEF;"| 5870 || 355 || 1.888 || 188 || 900? || 1600 || 2.1 || PCI-E 2.1 x16 || poclbm/Linux ||
|-
|style="background:#EFFFEF;"| 5870 || 340 || 1.809 || 188 || 850 || 1600 || || PCI-E 2.1 x16 || m0mchil's OpenCL || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26363#msg26363 source]
|-
|style="background:#EFFFEF;"| 5870 || 360 || 1.6822 || 214 || 970 || 700 || || PCI-E 2.0 x16 || m0mchil's OpenCL w7-64 || -f 0 -v -w 128 [http://www.bitcoin.org/smf/index.php?topic=6144.msg91959#msg91959 source]
|-
|style="background:#EFFFEF;"| 5870 || 377 || 2.008 || 188 || 850 || 1600 || || PCI-E 2.0 x16 || hashkill-0.2.5 alpha || -D -G2
|-
|style="background:#EFFFEF;"| 5870 || 408 || 1.8888 || 216 || 980 || 1600 || 2.1 || PCI-E 2.0 x16 || poclbm/Win7x64 || -f 20 -v -w 128, BIT_ALIGN, BFI_INT
|-
|style="background:#EFFFEF;"| 5870 || 400 || 1.9047 || 210 || 950 || 1600 || 2.4 || PCI-E 2.0 x8 || Phoenix 1.3 || -k poclbm VECTORS AGGRESSION=7 FASTLOOP BFI_INT
|-
|style="background:#EFFFEF;"| 5870 || 398 || 1.980 || 201 || 900 || 1600 || || PCI-E 2.0 x16 || hashkill-0.2.5 alpha || -D -G2 (GPU OC to 900, memory downclocked to 900)
|-
|style="background:#EFFFEF;"| 5870 || 420 || 2.0000 || 210 || 950 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.48 || -k phatk VECTORS BFI_INT AGGRESSION=14 WORKSIZE=256 -- Memory Clock 300Mhz
|-
|style="background:#EFFFEF;"| 5870 || 421 || 1.9581 || 215 || 975 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix 1.47 || VECTORS BFI_INT AGGRESSION=13 -k phatk
|-
|style="background:#EFFFEF;"| 5870 || 440 || 2.0000 || 220 || 995 || 1600 || 2.4 || PCI-E 2.0 x16 || Phoenix ||
|-
|style="background:#EFFFEF;"| 5870 || 438 || 1.9819 || 221 || 1000 (OC) || 1600 || 2.1 || PCI-E 2.0 x16 || poclbm/Linux || -v -w 64 -f 1
|-
|style="background:#EFFFEF;"| 5870 || 445 || || || 1040 || 1600 || 2.1 || PCI-E 2.0 x16 || poclbm/Windows 7 64 || -v -w 128 -f 1 Crossfired, Water cooled, 890 Mhash/s total, Both cards peak at 450 Mhash/s. Best dual gpu setup me thinks?
|-
|style="background:#EFFFEF;"| 5870 || 435 || || || 990 || 300 || 2.4 || PCI-E 2.0 x8 || LinuxCoin v0.2b phoenix/phatk || (Powercolor brand) -k phatk VECTORS BFI_INT WORKSIZE=256 AGGRESSION=11 FASTLOOPS=false
|-
|style="background:#FFEFEF;"| 5970 || 530 || 1.803 || 294 || 725 || 3200 || 2.4.595.10 || PCI-E 2.1 x16 || poclbm/201103.beta3/Windows || -v -w128 -f60
|-
|style="background:#FFEFEF;"| 5970 || 535.06 || 1.820 || 294 || 725 || 3200 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
|style="background:#FFEFEF;"| 5970 || 560 || 1.905 || 294 || 725 || 3200 || || PCI-E 2.1 x16 || Diablo ||
|-
|style="background:#FFEFEF;"| 5970 || 565 || 1.922 || 294 || 725 || 3200 || 2.1 || PCI-E 2.1 x16 || clmine2 ||
|-
|style="background:#FFEFEF;"| 5970 || 604 || 2.054 || 294 || 725 || 3200 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
|style="background:#FFEFEF;"| 5970 || 645 || 1.875|| 344 || 850 || 3200 || 2.1 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || -f1, Debian 6, fglrx-driver 10.9.3
|-
|style="background:#FFEFEF;"| 5970 || 740 || 2.1511 || 344 || 850 || 3200 || 2.1 || PCI-E 2.1 x16 || phoenix/1.3 || AGGRESSION=12 WORKSIZE=128 VECTORS BFI_INT, memory clock @ 300MHz
|-
|style="background:#FFEFEF;"| 5970 || 755 || 2.2076 || 342 || 848 || 3200 || 2.1 || PCI-E 2.1 x16 || poclbm 28-04-11 || -f 1 -w 256 -v, Ubuntu 10.10, fglrx 11.4, memory clock @ 300MHz
|-
|style="background:#FFEFEF;"| 5970 || 802 || 2.31 || 347 || 850 || 3200 || 2.4 || PCI-E 2.1 x16 || phoenix poclbm Ubuntu 11.04 || -q 6 -k AGGRESSION=19 WORKSIZE=128 BFI_INT VECTORS, fglrx 11.4, mem clock @ 1000MHz
|-
|style="background:#EFFFEF;"| 5870x2 (Ares) || 620 || || || 850 || 3200 || 2.1 || PCI-E 2.1 x16 || guiminer || -v -w 128
|-
|style="background:#EFFFEF;"| 5870x2 (Ares) || 826 || 0.751 || 1100 || 950 || 3200 || 2.1 || PCI-E 2.1 x16 || phoenix 1.4 w/ Phtak || AGGRESSION=13 WORKSIZE=128 VECTORS BFI_INT Memory @ 300MHz
|-
|style="background:#EFFFEF;"| 5870x2 (Ares) || 826 || 1.18 || 700 || 935 || 3200 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 w/ Phatk || AGGRESSION=13 WORKSIZE=256 VECTORS BFI_INT FASTLOOP=false, memory @ 319 MHz, Windows 7 32-bit
|-
|style="background:#EFFFEF;"| 5870x2 (Ares) || 878 || 0.585 || 1500 || 1000 || 3200 || 2.1 || PCI-E 2.1 x16 || phoenix 1.7 w/ Phtak || AGGRESSION=13 WORKSIZE=128 VECTORS BFI_INT Memory @ 300MHz
|-
| 6310M || 9.821 || 0.545 || 18 || 500 || 80 || 2.4 || Integrated/APU || poclbm-gui -v -w128 || HP DM1z 18W TDP is shared with the CPU
|-
| 6470M || 24.1 || || || || || 2.1 || Integrated/APU || guiminer ||
|-
| 6470M || 31.0 || || || || || 2.1 || Integrated/APU || phoenix 1.48 ||
|-
| 6490M || 16.289 || 0.708 || 23 || || || || PCI-E 2.1 x16 || poclbm-mod (Mac OS X 10.6.7) || MacBook Pro early 2011
|-
| 6490M || 15.21 || || || || || || || [http://forum.bitcoin.org/index.php?topic=8994.0 DiabloMiner GUI] v2011-05-22 / Mac OS X 10.6.7|| Model: MacBookPro8,2 VRAM: 256MB
|-
|style="background:#FFDD00;"| 6570 || 68.0 || 1.133 || 60 || 650 || 480 || 2.4 || PCI-E x16 || guiminer 2011-05-21 with poclbm (Win7-32bit)|| no extra option for miner . Sapphire 6570 gddr5 512mb
|-
|style="background:#FFDD00;"| 6570 || 82.1 || 1.368 || 60 || 650 || 480 || 2.4 || PCI-E x16 || guiminer 2011-05-21 with poclbm (Win7-32bit)|| -v -w128 . Sapphire 6570 gddr5 512mb
|-
| 6750 || 167.59 || || || 870 || || || PCI-E 2.1 x16 || guiminer || -v -f30 -w128
|-
| 6770 || 180 || || || 850 || 1200 || || || guiminer || -v -w128 , this was an XFX (OEM) model, GPU @ 850 MHz, mem @ 1200 MHz; I pushed it up to 190 Mhash/s briefly by overclocking, but it crashed the system above that
|-
| 6790 || 220 || || 150 || 800 || || || PCI-E 2.1 x16 || Phoenix 1.48 || -k phatk BFI_INT FASTLOOP AGGRESSION=12 VECTORS OC'd to 1ghz, underclocked mem to 300, voltage at 1175
|-
| 6850 || 171.59 || 1.351 || 127 || 775 || 960 || 2.1 || PCI-E 2.1 x16 || clmine ||
|-
| 6850 || 196 || || || 850 || 960 || || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 0
|-
|style="background:#EFEFFF;"| 6850 || 220 || 1.236 || 178[*] || 1000 || 960 || 2.4RC1 || PCI-E 2.1 x16 || poclbm || -v -w 128 -f 30 (*Overclocked wattage calculated [http://bakkap.free.fr/Misc/wCalc.html here] )
|-
| 6850 || 234.8 || || || 940 || 960 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.3 || AGGRESSION=8 WORKSIZE=128 VECTORS BFI_INT
|-
| 6850 || 244.2 || || || 960 || 960 || 2.1 || PCI-E 2.0 x16 || poclbm june-2011 || -v -w 128
|-
|style="background:#FFFF00;"| 6870 || 232.47 || 1.540 || 151 || 900 || 1120 || || PCI-E 2.1 x16 || poclbm -v -w 128 ||
|-
|style="background:#FFFF00;"| 6870 || 277.47 || || || 940 || 1120 || || PCI-E 2.1 x16 || Phoenix 1.3 || AGGRESSION=8 WORKSIZE=128 VECTORS BFI_INT
|-
|style="background:#FFFF00;"| 6870 || 271 || || 150 || 940 || 1100 || 2.4 || PCI-E 2.0 x16 || poclbm -v -w 128 || Debian 6.0.1 x86_64
|-
|style="background:#FFFF00;"| 6870 || 260.1 || 1.611 || 175 || 1001 || 1150 || 2.2 || PCI-E 2.1 x16 || poclbm-gui windows7x86 cat 11.3 || -v -w 128 -f 1
|-
|style="background:#FFFF00;"| 6870 || 276 || 1.828 (?) || 151 (?) || 900 || 1120 || 2.4 || PCI-E 2.1 x16 || hashkill-0.2.5 alpha cat 11.4 sdk 2.4 || -G2 -D stock clocks, debian linux 64bit
|-
|style="background:#FFFF00;"| 6870 || 300.06 || 1.830 || 164 || 1020 || 1120 || 2.4 || PCI-E 2.1 x16 || Phoenix 1.4 cat 11.4 || VECTORS BFI_INT AGGRESSION=8 fastloop mem clock 344
|-
|style="background:#FFFF00;"| 6870 || 306 || 1.748 (?) || 175 (?) || 1000 || 1120 || 2.4 || PCI-E 2.1 x16 || hashkill-0.2.5 alpha cat 11.4 sdk 2.4 || -G2 -D overclocked to 1000, debian linux 64bit
|-
|style="background:#FFFF00;"| 6870 || 300 || 1.72 || 174 || 1038 || 1120 || 2.4 || PCI-E 2.1 x16 || poclbm windows7x86 cat 11.4 || -v -w128 -f1 mem clock 360, fan 100% temp 73C
|-
|style="background:#FFFF00;"| 6870 || 310 || || || 1035 || 1120 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 phatk 11.5 sdk 2.4 || BFI_INT VECTORS FASTLOOP=false AGGRESSION=12 WORKSIZE=128, mem clock @ 300MHz, voltage @ 1.300
|-
|style="background:#FFFF00;"| 6870 || 322 || 1.882 || 170 || 1050 || 1120 || 2.4 || PCI-E 2.1 x16 || phoenix 1.47 phatk 11.5 sdk 2.4 || BFI_INT VECTORS FASTLOOP=false AGGRESSION=12 WORKSIZE=256, mem clock @ 400MHz
|-
|style="background:#FFFF00;"| 6870 || 329 || || || 1075 || 372 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48 phatk 11.5 sdk 2.4 || BFI_INT VECTORS FASTLOOP=false AGGRESSION=11 WORKSIZE=256
|-
| 6950 || 272 || || || 900 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1150 mV, AGGRESSION = 7, BFI_INT
|-
| 6950 || 291 || || || 920 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1200mV, AGGRESSION = 7, BFI_INT
|-
| 6950 || 295 || || || 930 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1275mV, AGGRESSION = 7, BFI_INT
|-
| 6950 || 300 || || || 940 || 1408 || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || max stable @ 1300mV, AGGRESSION = 7, BFI_INT
|-
| 6950 || 295 || || 160 (?) || 810 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || unlocked shaders, default mem 1250
|-
| 6950 || 314 || || (?) || 800 || 1408 || 2.4.595.0 || PCI-E 2.1 x16 || guiminer/poclbm 05-01-11 || -v -f30 -w128 default mem 1250 Stock Sapphire 6950 1gb
|-
| 6950 || 325 || || 200 (?) || 885 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || unlocked shaders, default mem 1250
|-
| 6950 || 340 || || (?) || 800 || 1536 || (?) || PCI-E 2.1 x16 || guiminer/poclbm 05-21-11 ||-v -f30 -w128 default mem 1250,Sapphire 6950 1gb, unlocked shaders
|-
| 6950 || 349 || || ~200 || 800 || 1408 || || PCI-E 2.1 x16 || guiminer/poclbm 05-21-11 ||-v -f30 -w128, xfx 6950 xxx 1gb, locked shaders, core 900, mem 650, 79° C
|-
| 6950 || 360 || || 200 (?) || 970 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || unlocked shaders, default mem 1250
|-
| 6950 || 360 || || (?) || 870 || 1375 || (?) || PCI-E 2.1 x16 || guiminer/poclbm ||flashed with 6970 BIOS, -v -f30 -w128
|-
| 6950x4 || 1316 || 1.513 || 870 || 840 || 1408 || 2.4.595.0 || PCI-E 2.1 x16 || m0mchil/poclbm 03-07-11 || locked shaders, default mem 1250, dual fan 75C typical
|-
| 6950 || 417 || || +200? || 975 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || guiminer/poclbm || unlocked shaders, +20% overdrive, mem @ 1250, fan @ 77%, temp 64C, -v -w128, gpu core @ 1145mV
|-
| 6950 || 428 || || +200? || 1000 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || guiminer/poclbm || unlocked shaders, +20% overdrive, mem @ 1250, fan @ 80%, temp 64C, -v -w128, gpu core @ 1160mV
|-
| 6950 || 432 || || +200? || 1000 || 1536 || 2.4.595.0 || PCI-E 2.1 x16 || guiminer/poclbm || unlocked shaders, +20% overdrive, mem @ 520, fan @ 80%, temp 76C, -v -w128 -f 2, gpu core @ 1275mV
|-
|style="background:#F0FF0F;"| 6970 || 323 || 1.468 || 220 || 880 || 1536 || 2.3 || PCI-E 2.1 x16 || poclbm || -w 64, SDK 2.1 not supported on 69xx.
|-
|style="background:#F0FF0F;"| 6970 || 372 || || 220 (?) || 900 || 1536 || 2.4 || PCI-E 2.1 x16 || phoenix (svn trunk 05.14.2011) || clock 900/1375, VECTORS BFI_INT AGGRESSION=11 WORKSIZE=128, fan 45% (auto) / temp 90C
|-
|style="background:#F0FF0F;"| 6970 || 385 || 1.964 || 196 || 900 || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm || -v -w128, memory downclocked to 684Mhz, fan @ 70%/temp 81C
|-
|style="background:#F0FF0F;"| 6970 || 380 || || || || || 2.4 || PCI-E 2.1 x16 || poclbm || -v -w128 export GPU_USE_SYNC_OBJECTS=1 # to reduce poclbm CPU from 100% to 2%
|-
|style="background:#F0FF0F;"| 6970 || 403 || || (?) || MAX || 1536 || 2.4 || PCI-E 2.1 x16 || guiminer/poclbm || clock Max/50%+stock, -v -w128, fan= 100%/temp 72C (Note: Overclocked using CCC utility under Windows 7, Clock set to Max value w/ 50% increase to memory and 5% increase to voltage)
|-
|style="background:#F0FF0F;"| 6970 || 423 || || || 995 || || 2.4 || PCI-E 2.1 x16 || phoenix 1.48/poclbm || ATI Tray Tools, Clocks=995/331.25, WORKSIZE=128 BFI_INT AGGRESSION=11 VECTORS ,68C @ 65% Fan, HAF932 Case
|-
|style="background:#F0FF0F;"| 6970x2 || 710 || || || 900/880 || 1536 || 2.2 || PCI-E 2.1 x16 || poclbm || -w 256
|-
| 6990 || 670 || 1.94 || 346 || 830 || 3072 || 2.4 || PCI-E 2.1 x16 || poclbm || Catalyst 11.4 [http://forum.bitcoin.org/index.php?topic=2949.msg106238#msg106238 source].
|-
| 6990 || 708 || 2.05 || 346 || 830 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || BIOS switch at "default" position 2, see [http://www.bitcoin.org/smf/index.php?topic=2949 source]
|-
| 6990 || 746 || 1.82 || 410 || 880 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || BIOS switch at "overclocked" position 1, see [http://www.bitcoin.org/smf/index.php?topic=2949 source]
|-
| 6990 || 758 || || || 880 || || 2.4 || || Phoenix with Poclbm || Catalyst 11.4, OC switch ON, VECTORS AGGRESSION=12 BFI_INT WORKSIZE=128 FASTLOOP=false
|-
| 6990 || 771 || 1.8804 || 410 || 880 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || SDK 2.1 not supported on 69xx. Memory clock @ 1280Mhz.
|-
| 6990 || 772 || 1.8380 || 420 || 900 || 3072 || 2.3 || PCI-E 2.1 x16 || Phoenix & Poclbm || OC switch ON + overclocked to 900 mhz, VECTORS AGGRESSION=12 BFI_INT WORKSIZE=128
|-
| 6990 || 790 || || || 900 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || BIOS switch at "overclocked" position 1; with "aticonfig --odsc=900,1260" to further overclock the GPU to 900 MHz and mem to 1260 MHz, see [http://www.bitcoin.org/smf/index.php?topic=2949 source]
|-
| 6990 || 802 || || || 915 || 3072 || 2.3 || PCI-E 2.1 x16 || mrb's hdminer || BIOS switch at "overclocked" position 1; with "aticonfig --odsc=915,1260" to further overclock the GPU to 915 MHz and mem to 1260 MHz, see [http://www.bitcoin.org/smf/index.php?topic=2949 source]
|-
| 6990 || 835 || || || 890/860 || 3072 || 2.4 || PCI-E 2.1 x16 || phoenix || BIOS switch at "overclocked" position 1; with "aticonfig --adapter=1 --odsc=990,890 and aticonfig --adapter=0 --odsc=960,860" (GPU 0 runs hot). Currently, aticonfig can only underclock RAM to 100mhz below core speed. Command line: phoenix.py -k poclbm VECTORS AGGRESSION=13 WORKSIZE=128 BFI_INT
|-
| 6990x2 || 1436 || 1.848 || 777 || 880 || 6144 || 2.4 || PCI-E 2.0 x16 x2 || guiminer 2011.05.11 || AUSUM switch set to 1 on both cards; Core left at 880MHz, memory left at 1250MHz; VECTORS AGGRESSION=12 BFI_INT WORKSIZE=128
|-
| 6990x3 || 2094 || || || 900 || || 2.4 || PCI-E 2.0 x16 x8 x4 || poclbm || GPU 900MHz, Memory 1250MHz; poclbm.py -f 0 -w 256
|-
|FirePro V4800 || 79.7 || || || 775 || 400 || 2.4 || PCI-E 2.1 x16 || GUIMiner v2011-05-01 ||
|-
|FirePro V8700 || 84.8 || || || 750 || 800 || || || poclbm-mod.03.24.2011 ||
|-
|FirePro M5800 || 61.4 || || || 650 || || || || poclbm-mod.03.24.2011 || Ubuntu
|-
|FirePro V5800 || 118.9 || || || || 800 || || PCI-E 2.0 x16 || GUIMiner v2011-05-01 || Windows 7 32bit
|-
|FirePro V7750 || 35.7 || || || || || 2.4 || PCI-E 2.0 x16 || GUIMiner v2011-05-21 || Windows 7 64bit
|-
|FirePro M7820 || 153.0 || || || 700 || 800 || 2.1 || PCI-E 2.1 x16 || GUIMiner v2011-05-21 || Memory downclocked to 500 from 1000MHz, 172MH/s@800MHz, 184MH/s@860Mhz (max.), only SDK2.1 works, Windows 7 x86
|-
|}

===Nvidia===

{| class="wikitable sortable"
|-
! Model !! Mhash/s !! Mhash/J !! W !! Clock !! SP !! Comment
|-
| ION || 1.8 || || 27 || || 16 || poclbm; power consumption incl. CPU
|-
| 8200 mGPU || 1.2 || || || 1200 || 16 || 128 MB shared memory, "poclbm -w 128 -f 0"
|-
| 8400 GS || 2.3 || || || || || "poclbm -w 128"
|-
| 8400 GS || 1.6 || || 128 || 1238 || || DiabloMiner -w 128 -f 1 [https://en.bitcoin.it/wiki/User:Knightmb source]
|-
| 8400M GS || 2.0 || || || || ||
|-
| 8600M GT || 4.93 || || || || 32 ||
|-
| 8600GT || 5.66 || || || 1188 || 32 ||
|-
| 8600GT OC || 7.3 || || || 1602 || 32 || [http://www.bitcoin.org/smf/index.php?topic=1334.0 poclbm] -w 128 [http://www.bitcoin.org/smf/index.php?topic=4967.msg72833#msg72833 source]
|-
| 8800GT || 25 || 0.24 || 105 || 1300 || ||
|-
| 8800GT || 24.5 || 0.23 || 105 || 1300 || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source]
|-
| 8800GT || 31.1 || || 105 || 1855 || || Overclocked 715 GPU / 1030 Memory / 1855 Shader; GuiMiner v2011-05-21
|-
| 8800GT || 31.8 || || 105 || 1836 || 112 || 713 gpu, 1026 memory. win7x86, phoenix 1.48, -k poclbm WORKSIZE=64 AGGRESSION=5
|-
| 8800GTS || 16.8 || 0.109 || 154 || || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg25069#msg25069 source] [http://www.techspot.com/review/79-geforce-8800-gts-512/page11.html source]
|-
| 8800 GTS || 18.7 || 0.124 || 150 || 1200 || || poclbm -w 64 no vectors
|-
| 8800m GTX || 16.3 || || || || || rpcminer-cuda Win7-64
|-
| 9300GE || 1.57 || || || 1300 || 8 ||
|-
| 9300GS || 1.69 || || || 1400 || 8 ||
|-
| 9300/nForce 730i || 2.15 || || || 1200 || 16 ||
|-
| 9400GT || 3.37 || 0.067 || 50 || 1400 || 16 ||
|-
| 9400M (MacBook) || 1.90 || 0.32 || 6 || 700 || || poclbm -f 8 no vectors
|-
| 9500GT || 6.75 || 0.135 || 50 || 1400 || 32 ||
|-
| 9600GSO || 19.88 || 0.237 || 84 || 1375 || 96 ||
|-
| 9600GSO512 || 11.75 || 0.131 || 90 || 1625 || 48 ||
|-
| 9600GT || 15.66 || 0.165 || 95 || 1625 || 64 ||
|-
| 9600GT Zotac || 15 || || || 1650 || 64 ||
|-
| 9600GT OC || 18.8 || <0.198 || >95 || 1981 || 64 || [http://www.bitcoin.org/smf/index.php?topic=1334.0 poclbm] -w 128 -f 10 [http://www.bitcoin.org/smf/index.php?topic=4967.msg74610#msg74610 source] [http://www.bitcoin.org/smf/index.php?topic=4967.msg73353#msg73353 source]
|-
| 9800GT || 30.36 || 0.289 || 105 || 1800 || 112 ||
|-
| 9800GT OC || 29.5 || 0.283 || 105 || 1836 || 112 || poclbm.py, no options. Memory underclocked to 850Mhz, GPU overclocked to 733Mhz
|-
| 9800GTX || 32.54 || 0.232 || 140 || 1688 || 128 ||
|-
| 9800GTX+ || 35.39 || 0.251 || 141 || 1836 || 128 ||
|-
| 9800GTX+ || 37.23 || 0.266 || 140 || 1890 || 128 || win7x64 275.27 phoenix(1.48) -k poclbm AGGRESSION=3 WORKSIZE=64
|-
| 9800GTX+ || 40.20 || || 140 || 835 || 128 || lowered memory clock higher core, unstable if going higher
|-
|style="background-color:#FFEFEF"| 9800GX2 || 57.83 || 0.294 || 197 || || 2x128 ||
|-
|style="background-color:#FFEFEF"| 9800GX2 || 28 || 0.142 || 197 || || 2x128 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37620#msg37620 source]
|-
| G210 || 3.38 || 0.111 || 30.5 || 1402 || 16 ||
|-
| G210 || 3.79 || 0.124 || 30.5 || 1402 || 16 || poclbm -f 1
|-
| GT220 || 10.8 || || 128 || 1360 || || DiabloMiner -w 128 -f 1000 [https://en.bitcoin.it/wiki/User:Knightmb source]
|-
| GT240 || 19.37 || 0.281 || 69 || 1340 || 96 ||
|-
| GT240 || 21.24 || || || || 96 || [http://www.bitcoin.org/smf/index.php?topic=4291.0 poclbm-mod] -f 0 -v [http://www.bitcoin.org/smf/index.php?topic=4967.msg73383#msg73383 source]
|-
| GTS250 || 35.39 || 0.244 || 145 || 1836 || 128 ||
|-
| GTS250 || 35.2 || 0.243 || 145 || 1836 || 128 ||
|-
| GTS250 OC || 37 || 0.255 || 145 || 2047 || 128 ||
|-
| GTX260M || 22.5 || || || 500 || 112 || poclbm 4/28/2011 Asus G71GX runs ~90c without cooling pad
|-
| GTX260 || 35.91 || 0.178 || 202 || 1242 || 192 ||
|-
| GTX260 || 44 || 0.242 || 182 || 1242 || 216 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
| GTX260c216 || 40.40 || 0.236 || 171 || 1242 || 216 ||
|-
| GTX260c216 || 47.4 || || 182 || 1348 || 216 || poclbm -w 256
|-
| GTX260c216 || 50.00 || || || 1050 || 216 || m0mchil GPU client, Windows 7 64-bit, x6 @ 3.5ghz
|-
| GTX260c216 OC || 52.0 || || || 1461 || 216 || "poclbm -w 256 -f 1"
|-
| GTX260c216 OC || 58.9 || || || 756/400 || 216 || Core overclocked, Memory underclocked, Ubuntu 11.04 Classic Session(No Effects) "poclbm -w 256 -f 1"
|-
| GTX275 || 50.75 || 0.232 || 219 || 1404 || 240 ||
|-
| GTX275 || 58 || || || 729/1458 || 240 || poclbm -f 0 -w 256
|-
| GTX280 || 46.84 || 0.198 || 236 || 1296 || 240 ||
|-
| GTX280 || 64.34 || 0.289 || 245 || 1296 || 240 || phoenix.exe -k poclbm AGGRESSION=6 WORKSIZE=128 (61*C with Accelero XTREME GTX280)
|-
| GTX285 || 64.8 || || || 1607 || 240 || GuiMiner - Not sure about wattage yet. Still testing. Card runs around 74 C
|-
|-
| GTX285 || 53.35 || 0.262 || 204 || 1476 || 240 ||
|-
| GTX295 || 89.78 || 0.311 || 289 || 1242 || 480 ||
|-
| GTX295 || 117.30 || || 289 || 1476 || 490 ||
|-
| GT 320M (MacBook Air) || 6.12 || || || 1212 || 48 ||
|-
| 320M (Mac mini 2010) || 7.0 || 0.35 || 20 || 450 || 32 || poclbm no extra options, windows 7 x64
|-
| GT 330M || 7.97 || || || || || Model: MacBookPro6,2 VRAM: 512MB Software: [http://forum.bitcoin.org/index.php?topic=8994.0 DiabloMiner GUI] v2011-05-22 / Mac OS X 10.6.7
|-
| GT 330M (Sony Vaio Z) || 7.8 || 0.71 ( 0.3 total) || 11 (26w total) || 1045 || 48 ||
|-
| GTS 350M (Toshiba A665-3DV) || 17.0 || || 14 || 1080 || || DiabloMiner-Windows.exe
|-
| GTS 360M || 25.0 || || || || || [toshiba qosmio laptop, ~150-165*F stock fans]
|-
| GTS 360M (ASUS G60jx) || 20.0 || || || || || everythins is stock, it cannot sustain. it reaches 90 degrees and freezes.
|-
| GT430 || 20.24 || 0.413 || 49 || 1400 || 96 ||
|-
| GTS450 || 45.28 || 0.427 || 106 || 1566 || 192 ||
|-
| GTX460SE || 56.39 || 0.376 || 150 || 1300 || 288 ||
|-
| GTX460 || 66.32 || || || 814 || 336 || rpcminer-cuda 20110605, Graphics Clock @ 814MHz, Memory @ 1555MHz
|-
| GTX460 || 68.31 || 0.427 || 160 || 1350 || 336 ||
|-
| GTX460 768MB || 57.8 || || ? || 1350 || 336 || rpcminer-cuda -gputhreads=320 -gpugrid=336
|-
| GTX460 (2 cards) || 102 || 0.319? || 320? || 1350 || || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26363#msg26363 source]
|-
| GTX460 (2 cards) OC || 127 || 0.374 || 340 || 1620 || 2x 336 || [http://www.bitcoin.org/smf/index.php?topic=2444.0 rpcminer-cuda] -gpugrid=128 -gputhreads=128 ver.20110227
|-
| GTX465 || 64.41 || 0.322 || 200 || 1215 || 352 ||
|-
| GTX470 || 81.98 || 0.381 || 215 || 1215 || 448 ||
|-
| GTX470 || 94.7 || || || 1414 || ||
|-
| GTX470 || 111.9 || || 215 || 1650 || 448 ||
|-
| GTX470 || 115 || || || 1616 || || phoenix 1.46 poclbm VECTORS BFI_INT FASTLOOP AGGRESSION=6
|-
| GTX480 || 101.28 || 0.405 || 250 || 1401 || 480 ||
|-
| GTX560 Ti || 67.7 || 0.39 || 170 || 1700 || 384 || standard EVGA 560, no overclock
|-
| GTX560 Ti || 74.8 || 0.41 || 180 || 1700 || 384 || gigabyte 900Mhz clock; -w 512 -v
|-
| GTX560 OC || 86.7 || <0.51 || >170 || 1800 || 384 || [http://www.bitcoin.org/smf/index.php?topic=2444.0 rpcminer-cuda] [http://www.bitcoin.org/smf/index.php?topic=4967.msg72816#msg72816 source]
|-
| GTX570 || 105.83 || 0.483 || 219 || 1464 || 480 ||
|-
| GTX580 || 140.05 || --- || 244 || 1544 || 512 ||
|-
| GTX590 || 193.1 || --- || --- || 1215 || 2x 512 || poclbm -v -w 256, Win
|-
| Quadro FX 580 || 5.7 || 0.14 || 40 || 1125 || 4 ||rpcminer-cuda, Win, -gpugrid=128 -gputhreads=512
|-
| Quadro FX 770M || 5.75 || || || 500 || 32 || DiabloMiner-Windows.exe BFI_INT FASTLOOP AGGRESSION=6, Win
|-
|Quadro FX 770M || 6.39 || || || 500 || 32 || DiabloMiner-Windows.exe BFI_INT FASTLOOP AGGRESSION=6 w 64, Win 7x64
|-
|Quadro FX 880M || 9.6 || || || || || poclbm/guiminer
|-
| Quadro FX 1600M || 6 || 0.12 || 50 || 625 || 32 ||rpcminer-cuda, Win
|-
| Quadro FX 3600M || 36 || -- || 70 || 500 || 96 ||DiabloMiner, win
|-
| Quadro NVS 135M || 1.05 || 0.1 || 10 || 800 || 1 ||
|-
| Quadro NVS 3100M || 3.6 || 0.257 || 14 || 600 || 16 || rpcminer-cuda, Win, CUDA 3.1.1
|-
| Tesla C1060 || 52.5 || || || 1296 || 240 || poclbm, Win7x64
|-
| Tesla M2050 || 79.8 || || || 1550 || 448 || DiabloMiner
|-
| Tesla M2050 || [http://glennfrancismurray.com/cost-defective-mining-with-gpu-clusters-amazo 100] || 0 || 0 || - || 512 || Amazon AWS [http://glennfrancismurray.com/cost-defective-mining-with-gpu-clusters-amazo CUDA RPC Miner & CUDA 2.0]
|-
| Tesla S1070 || 155.2 || || || || || rpcminer-cuda, Linux, CUDA 3.2, 4 instances (-gpu=0 through -gpu=3)
|-
| GTX280x2 || 102.7 || || || || ||
|-
|}

==CPUs/APUs==

A lot of nice data can be pulled from [http://www.bitcoin.org/smf/index.php?topic=1628.0 this thread] to seed this section.

Might you wish to throttle CPU load a bit, so it doesn't reach 100°C, it can be done with Battle Encoder Shirase to a margin, like, -15% of available CPU cycles.

Often, the best combination to be is to throttle CPU miner to -5% '''AND''' set it to least of priority levels, so as not to choke GPU miner up.

===AMD===
{| class="wikitable sortable"
|-
! Model !! nprocs !! Mhash/s !! Mhash/J !! TDP [W] !! CPU Clock !! Mhash/s CPU !! Mhash/s GPU !! GPU !! GPU Clock !! SP !! Software !! Notes
|-
| 4x Opteron 6174 || 48 || 115 || 0.36 || 320W || 2.2 GHz || 2.4
|colspan=4|
| cpuminer v0.8.1 || --alg 4way --threads 48
|-
| 2x Opteron 6128 || 16 || 32.4 || 0.141 || 230W || 2 GHz || 32.4
|colspan=4|
| 0.3.19 || -4way
|-
| Athlon XP 2000+ || 2 || 0.62 || 0.009 || 70W || 1.67 GHz || 0.62
|colspan=4|
| 0.3.18/Ubuntu || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source] [http://www.pcstats.com/articleview.cfm?articleid=914&page=4 source]
|-
| Athlon 64 3500+ || 1 || 1.18 || 0.013 || 89W || 2.54 GHz || 1.18
|colspan=4|
| ufasoft v0.4 || overclocked (originally 2.2 GHz)
|-
| Athlon 64 X2 3800+ || 2 || 1.73 || 0.03 || 65 W || 2.00 GHz || 1.73
|colspan=4|
| cpuminer (v0.8.1-1-g69529c3) || -algo=4way
|-
| Athlon 64 X2 4000+ || 2 || 1.9 || 0.02 || 65W || 2.1 GHz || 1.9
|colspan=4|
| rpc-miner ||
|-
| Athlon 64 X2 4400+ || || 2.09 || 0.032 || 65W || 2.3GHz || 2.09
|colspan=4|
| 0.3.19/Win x64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37592#msg37592 source]
|-
| Athlon 64 X2 6000+ || 2 || 2.81 || 0.02 || 125W || 3 GHz || 2.81
|colspan=4|
| || [http://www.bitcoin.org/smf/index.php?topic=1628.msg22881#msg22881 source]
|-
| Athlon 64 X2 6400+ Black Edition || 2 || 2.9 || 0.023 || 125W || 3.2 GHz || 2.9
|colspan=4|
| 0.3.20.2 BETA/Win 7 x64 || -4way
|-
| Athlon II X2 240e || 2 || 2.71 || 0.06 || 45W || 2.81 GHz || 2.71
|colspan=4|
| bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Athlon II X2 250 || 2 || 5.6 || 0.09 || 65W || 3.01GHz || 5.6
|colspan=4|
| bitcoin-miner 0.11 ||
|-
| Athlon II X4 630 || 4 || 10.7 || 0.11 || 95W || 2.8 GHz || 10.7
|colspan=4|
| bitcoin-miner 0.4 ||
|-
| Phenom II X3 720 || 3 || 3.8 || 0.04 || 95W || 2.8 GHz || 3.8
|colspan=4|
| 0.3.1x/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
| Phenom X4 9950 BE || 4 || 9.3 || 0.07 || 126W || 2.6 GHz || 2.32
|colspan=4|
| bitcoin-miner 0.13/WinXP || No GPU
|-
| Phenom II X3 720 || 3 || 7.2 || 0.08 || 95W || 2.8 GHz || 7.2
|colspan=4|
| cpu-miner 0.2.1/WinXP || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source]
|-
| Phenom II X4 810 || 4 || 5.0 || || 95W || 2.8 GHz ||
|colspan=4|
| rpcminer-cpu ||
|-
| Phenom II X4 810 || 4 || 9.5 || || 95W || 2.8 GHz ||
|colspan=4|
| rpcminer-4way ||
|-
| Phenom II X4 810 || 4 || 10.5 || || 95W || 2.8 GHz ||
|colspan=4|
| ufasoft v0.10 ||
|-
| Phenom II X4 955 || 4 || 11 || 0.09 || 125W || 3.2 GHz || 11
|colspan=4|
| rpcminer-4way ||
|-
| Phenom II X4 965 || 4 || 12 || 0.09 || 140W || 3.4 GHz || 11
|colspan=4|
| rpcminer-4way ||
|-
| Phenom II X6 1055T || 6 || 15.84 || 0.13 || 125W || 2.82 GHz || 15.84
|colspan=4|
| bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Phenom II X6 1090T || 6 || 18|| || 141W|| 3.50 GHz || 3
|colspan=4|
| minerd ||
|-
| Phenom II X6 1100T || 6 || 22 || 0.176 || 125W || 3.82 GHz || 22
|colspan=4|
| bitcoin-miner || Aciid#bitcoin-dev
|-
| Zacate E-350 || 2 || 11 || 0.615 || 18W || 1.6 Ghz || 1.231 || 9.831 || HD6310M || 492 Mhz || 80 || poclbm -v -w128 + Ufasoft 0.7 || stock speeds
|-
| Zacate E-350 || 2 || 12
|colspan=2|
| 1.648 Ghz || 1.252 || 10.87 || HD6310M || 492 Mhz || 80 || poclbm -v -w 256 -f 1 || "autotune" speed with ASUS EFI BIOS
|}

===ARM===
{| class="wikitable sortable"
|-
! Model !! p/t !! Mhash/s !! Mhash/J !! ACP [W] !! Clock !! Version !! Comment
|-
| ARM1136EJ-S || 1 || 0.11 || ? || ? || 0.528 GHz || cpuminer git || T-Mobile Pulse, inside Debian chroot, 'c' algo
|-
| Cortex-A8 || 1 || 0.125 || 0.36 || 0.35 W || 0.6 GHz || cpuminer git (2011-03-26) || Nokia N900: 'cryptopp'
|-
| Cortex-A8 || 1 || 0.2 || 0.57 || 0.35 W || 0.6 GHz || cpuminer git (2011-03-26) || Nokia N900: 'c' algo
|-
| 2x Cortex-A9 || 2 || 0.57 || 1.14 || 0.5 W || 1.0 GHz || cpuminer git (2011-03-24) || Toshiba AC100, ubuntu, 'c' algo
|}

===Intel===
{| class="wikitable sortable"
|-
! Model !! p/t !! Mhash/s !! Mhash/J !! ACP [W] !! Clock !! Version !! Comment
|-
| Pentium III mobile ? || 1 || 0.3 || 0.014 || 21W || 1.07 GHz || 0.3.1x/Win2K || [http://www.bitcoin.org/smf/index.php?topic=1628.msg24699#msg24699 source] [http://ark.intel.com/Product.aspx?id=27380 source]
|-
| Pentium M 1.6ghz || 1 || .4 || || || 1.6 GHZ || minerd (jgarzik's 1.0) || cryppto, Windows 7
|-
| Pentium M 1.73ghz || 1 || .5 || || || 1.73 GHZ || minerd (jgarzik's 1.0) || cryppto, Windows 7
|-
| Old Xeon 512k (Dual) || 2x1/2 || 2.0 || ? || ? || 3.06GHz || cpuminer (v0.8.1-1-g69529c3) || HT disabled, algo=4way (twice as fast as the 2nd best algo)
|-
| Pentium 4 2.0A || 1 || 0.85 || || || 2.0 GHz || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft-0.4]/WinXP || -g no -t 2
|-
| Pentium Dual-Core E2180 || 2/2 || 1.75 || || || 2.0 GHz || rpcminer-cpu || Win7-64
|-
| Pentium Dual-Core E2180 || 2/2 || 4.1 || || || 2.0 GHz || cpuminer || sse2_64
|-
| Pentium Dual-Core E2180 || 2/2 || 4.5 || || || 2.0 GHz || ufasoft v0.11 || Win7-64
|-
| Pentium Dual-Core E5400 || 2/2 || 2.27 || 0.03 || 65W || 2.7 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Celeron E330 || 2/2 || 2.2 || 0.03 || 65W || 2.5 GHz || 0.3.19/Ubuntu10.04 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37620#msg37620 source]
|-
| Core 2 Quad Q6600 || 4/4 || 11.0 || || 105W || 2.40 GHz || bitcoin-miner 0.10 || -a 60 -g no -t 4
|-
| Core 2 Quad Q9400 || 4/4 || 11 || 0.046 || 95W || 2.66 GHz || bitcoin-miner 0.10 || -a 60 -g no -t 4
|-
| Core 2 Quad Q9650 || 4/4 || 18.67 || || 95W || 4.00 GHz || bitcoin-miner 0.10 || -a 60 -g no -t 4
|-
| Core i3 530 || 2/4 || 8.31 || 0.10 || 80W || 3.66 GHz || Ufasoft 0.7 || -v -a5 -g no -t 4
|-
| Core i3 M350 || 2/4 || 1.48 || 0.04 || 35W || 2.27 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Core i5 M450 || 2/4 || 1.8 || 0.05 || 35W || 1.2 GHz || 0.3.17/Win7-54 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg26292#msg26292 source]
|-
| Core i5-650 || 2/4 || 5.1 || 0.04 ? || || 3.2 GHz || cpuminer-0.7 || -4way
|-
| Core i5-750 || 4/4 || 14 || || || 3.2 GHz || bitcoin-miner 0.11 || -a 5 -g no -t 4
|-
| Core i5 ? || 4/? || 6.5 || || || || client from svn || [http://www.bitcoin.org/smf/index.php?topic=1628.msg37621#msg37621 source]
|-
| Core i5-2400 || 4/4 || 4.5 || 0.05 || 95W || 3.1 GHz || cpuminer git (2011-01-22) || cryptopp_asm32
|-
| Core i5-2400 || 4/4 || 14 || 0.15 || 95W || 3.1 GHz || cpuminer git (2011-03-26) || sse2_64
|-
| Core i7 620M || 2/4 || 1.888 || || || 2.66 GHz || [http://forum.bitcoin.org/index.php?topic=8994.0 RPCMiner GUI] v2011-05-22 / Mac OS X 10.6.7 || Model: MacBookPro6,2 RAM: 4GB
|-
| Core i7 920 || 4/8 || 19.2 || 0.10 || 195 || 4.0 GHz (x21) || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] || -a 5
|-
| Core i7 950 || 4/8 || 5.88 || 0.039 || 150W || 3.83 GHz (x23) || bitcoin-0.3.20.2 Win7-64 ||
|-
| Core i7 950 || 4/8 || 18.9 || 0.126 || 150W || 3.83 GHz (x23) || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] v0.4 ||
|-
| Core i7 980x || 6/12 || 19.2 || 0.15 || 130 || 4.4 GHz (x33) || cpuminer/Win7-64 ||
|-
| Core i7 980x || 6/12 || 8.7 || || || 3.9 GHz (x27) || 0.3.17/Win7-64 ||
|-
| Core i7 2635QM || 4/8 || 2.93 || || || 2.00 GHz || [http://forum.bitcoin.org/index.php?topic=8994.0 RPCMiner GUI] v2011-05-22 / Mac OS X 10.6.7 || Model: MacBookPro8,2 RAM: 4GB
|-
| Core i7 620M || 2/4 || 6.3 || 0.18 || 35 || 2.66 GHz || [http://www.bitcoin.org/smf/index.php?topic=3486.0 ufasoft] v0.4 ||
|-
| Core 2 Duo U7600 || 1 || 1.1 || || || 1.2 GHZ || minerd (jgarzik's 1.0) || cryppto, Windows 7
|-
| Core 2 Duo E5200 || 2/2 || 6.2 || 0.086 || 72W || 2.76 Ghz || Ufasoft/Win7-64 || TDP is 65W + 7W overclock
|-
| Core 2 Duo E6550 || 1/2 || 2.45 || ? || ? || 2.33 GHz || cpuminer 0.7.1 (Linux) || --algo=sse2_64
|-
| Core 2 Duo E6850 || 2/2 || 6.75 || 0.10 || 65W || 3.0 Ghz || ufasoft-0.3 ||
|-
| Core 2 Duo E7300 || 2/2 || 7.76 || 0.11 || 70W || 3.33 GHz (o/c?) || ufasoft-0.3 || miner optimized for Intel Core
|-
| Core 2 Duo E7300 || 2/2 || 2.52 || 0.04 || 65W || 2.66 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Core 2 Duo E8200 || 2/2 || 2.3 || 0.035 || 65W|| 2.66GHz || rpcminer-cpu || ||
|-
| Core 2 Duo E8400 || 2/2 || 6.9 || 0.106 || 65W || 3.0 GHz || ufasoft v0.10|| windows 7/64bit (-t 2)
|-
| Core 2 Duo T6400 || 2/2 || 4.2 || 0.12 || 35 W || 2.00 GHz || cpuminer git (Linux) || --algo=sse2_64
|-
| Core 2 Duo T7250 || 2/2 || 4.5 || 0.13 || 35 W || 2.00 GHz || bitcoin-miner 0.13/WinXP || No GPU
|-
| Core 2 Extreme X9000 || 2/2 || 2.37 || || || 2.8 GHz || rpcminer-cpu || Win7-64
|-
| Core 2 Extreme X9000 || 2/2 || 6.2 || || || 2.8 GHz || ufasoft v0.11 || Win7-64
|-
| Core 2 Extreme X9000 || 2/2 || 7.2 || || || 3.2 GHz || ufasoft v0.11 || Win7-64 Overclocked from 2.8 GHz to 3.2 GHz
|-
| Xeon 2.8 || 2/2 || 0.8 || || || 2.8 GHz || cpuminer || cryptopp_asm32
|-
| Xeon 3060 || 1/2 || 2.03 || 0.03 || 65W || 2.4GHz || cpuminer 0.8.1 (Linux) || --algo=cryptopp_asm32
|-
| Xeon Prestonia 2.4 (dual) || 2x1/2 || 2.16 || 0.017 || 130W || 2.4 GHz || ufasoft v0.4 ||
|-
| Xeon X5355 (dual) || 2x4/4 || 10.13 || 0.16 || 120W || 2.66GHz || bitcoind || Roughly the same speed as the "c" algo in cpuminer
|-
| Xeon X5355 (dual) || 2x4/4 || 22.76 || 0.09 || 120W || 2.66GHz || cpuminer (v0.8.1-1-g69529c3) || -O2 -march=core2, algo=sse2_64
|-
| Xeon E5335 || 4/4 || 9.35 || 0.12 || 80W || 2.00 GHz || ufasoft v0.11 || Vista-32
|-
| Xeon E5440 || 4/8 || 7.3 || ? || 80W || 2.66 GHz|| Kiv's poclbm-gui || FIXME: Either wrong model # or wrong threads/speed info
|-
| Xeon E5520 || 4/8 || 6.5 || 0.08 || 80W || 2.27 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Xeon E5530 || 4/8 || 7.14 || 0.09 || 80W || 2.4 GHz || bitcoind || [http://www.bitcoin.org/smf/index.php?topic=1628.msg19426#msg19426 source]
|-
| Xeon E5630 (dual) || 2x4/8 || 8 || 0.1 || 80W || 2.53 GHz || 0.3.17/Win7-64 || [http://www.bitcoin.org/smf/index.php?topic=1628.msg29471#msg29471 source]
|-
| Xeon E6520 (dual) || 2x4/8 || 24.7 || ? || ? || 2.53 GHz || ufasoft v0.10 || windows 2008 R2 64bit (-t 16)
|-
| Xeon E7520 (dual) || 2x4/16 || 18 || ? || 95W || 1.87 GHz || ufasoft v0.10 || windows 2008 R2 64bit (-t 16)
|-
| Atom N230 || 1/2 || 0.375 || || 4W || 1.6 GHz || rpcminer-cpu ||
|-
| Atom N230 || 1/2 || 0.245 || || 4W || 1.6 GHz || rpcminer-4way ||
|-
| Atom N230 || 1/2 || 0.97 || || 4W || 1.6 GHz || ufasoft v0.10 ||
|-
| Atom N270 || 1/2 || 1.19 || 0.24 || 5W || 1.6 GHz || ufasoft v0.10 ||
|}

===Other===
{| class="wikitable sortable"
|-
! Model !! p/t !! Mhash/s !! Mhash/J !! ACP [W] !! Clock !! Version !! Comment
|-
| Cell || 6 || 21 || 0.35 || 60W || 3.2 GHz || cellminer || Sony Playstation 3 (FAT): Needs custom firmware (no links to it, potential issues with Sony assholes.) [https://github.com/verement/cellminer source] [http://www.bitcoin.org/smf/index.php?topic=4704.20 source] Total power usage of PS3 fat is 120W but only the Cell cpu is active.
|-
| Cell || 6 || 21 || 0.7 || 35W || 3.2 GHz || cellminer || Sony Playstation 3 (SLIM): Total power usage of PS3 slim is 70W but only the Cell cpu is active.
|-
| MIPS || 1 || 0.026 || ? || ? || 200 MHz || cpuminer || ASUS WL-500G Deluxe router running [http://openwrt.org/ OpenWrt]
|-
| VIA Eden || 1 || 1.3 || 0.17 || 8W || 1600 MHz || cpuminer || VIA Eden w/ Padlock
|-
| PowerPC 7447A || 1 || 0.53 || || || 1420 MHz || cpuminer ||
|}

==See Also==

* [[Mining rig]]
* [[Generation Calculator]]
* [[Power Calc]]
* [[OpenCL miner]]
* [http://www.pcper.com/article.php?aid=745 ATI Stream vs. NVIDIA CUDA - GPGPU computing battle royale]
* [http://bitminer.info/ Bitminer.info] ('''WARNING''': Runs Java miner... May cause reduced computer performance)

[[Category:Mining]]