Topic: Post Your Hash/Sec and Hardware - page 2. (Read 39078 times)

Core 2 Duo 6600 (2.4 GHz, 4MB cache)
2GB RAM
Debian Linux, kernel 2.6.34.1
BitCoin 0.3.0 Beta (32-bit x86), with custom SSE hash code

Very responsive. No significant change in interactive response.

1 thread: ~4200 khash/s
2 threads: ~7700 khash/s

EDIT: For reference, I was getting about 875 khash/s (two threads) with the stock client and platform-specific compile options (-O3 -march=nocona -msse -msse2 -mfpmath=sse,387). Reorganizing sha.cpp, within the bounds of plain C code, pushed that up to ~1000 khash/s.

dual Intel Xeon 5570
.    8 cores (hyperthreaded to 16) @ 5%-10% used
.    32GB memory @ 20% used
.    Windows Server 2008 x64 with Hyper-V
.         guest Windows Server 2008 x64
.         4 cores @ 100%
.         4GB memory @ 24% used
.         Bitcoin x64
.              8 connections
.              68,226 blocks
.              ~2,250 khash/s
.         system very responsive

I've been comparing various setups on the same server, namely ...

Quad-Core AMD Opteron 2376
8GB memory

In all cases, I'm accessing the net via anonymous VPN.

I get the best results with Ubuntu 10.04 Desktop, installed via wubi on a 1TB WD RE3 7200rpm SATA ...

Ubuntu 10.04 Desktop x86
          Bitcoin x86
          15 connections
          67,556 blocks
          ~1,900 khash/s
          4 cores @ 100%
          system very responsive

Ubuntu 10.04 Desktop x64
          Bitcoin x64
          15 connections
          67,689 blocks
          ~2,150 khash/s
          4 cores @ 100%
          system very responsive

I've also looked at various VMs running on Windows Server 2008 x64 Standard with Hyper-V.  All of the guests live on the 1TB WD RE3 7200rpm SATA, and all have 4 CPUs and 4GB memory.  I get ...

Windows Server 2008 x64 Standard guest
          apparently para-virtualized
          Bitcoin x64
          8 connections
          67,561 blocks
          ~1,700 khash/s = 89% of native
          4 cores @ 100%
          system very responsive

Windows 7 x64 guest
          apparently not para-virtualized
          Bitcoin x64
          8 connections
          appears stuck at 1,581 blocks
          ~1,270 khash/s
          4 cores @ 100%
          system very responsive

Windows XP SP3 x86 guest
          apparently not para-virtualized
          Bitcoin x86
          8 connections
          67,578 blocks
          ~1,700 khash/s
          4 cores @ 100%
          system very responsive

Ubuntu 10.04 x86 guest
          apparently totally not para-virtualized
          Bitcoin x86
          15 connections
          67,609 blocks
          300-400 khash/s
          4 cores @ 100%
          system sluggish (even without Bitcoin)

More results coming soon 

Bitcoin 32-bit
Ubuntu 10.04 64-bit
AMD Phenom II X4 810 2.61Ghz
2150 khash/sec

Bitcoin 64-bit is faster than Bitcoin 32-bit by 300khash/sec, or one old laptop!

Bitcoin 64-bit
Ubuntu 10.04 64-bit
AMD Phenom II X4 810 2.61Ghz
2450 khash/sec

So, somewhat faster than in Windows 7. However, ubuntu lags a lot more than Windows does when Bitcoin is going fullbore.

2x Quad-Core Xeon E5335 @ 2 GHz
24GB FB-DIMM DDR2 667
4150 khash/s

I'm using the binaries straight from the site. I'll probably compile it later today and see if I can squeeze out a bit more performance.

Hi all, I'm getting 3440 khash/sec on my HP Z600 desktop with the following specs:

• OS: Windows 7 Professional 64-bit
• Processor: Intel Xeon E5520 @ 2.26 GHz (2 processors)
• RAM: 4GB

Bitcoin is running on 8 cores.

Fedora 13 64-bit
Intel Core i7 930 @ 2.8GHz
4 Cores, Hyper Threading on but using only 4 threads.
Uncertain on temps as of yet.

2800kh/s

Windows 7 64-bit
AMD Phenom II X4 810 2.61Ghz
2000 khash/sec
CPU temperature stabilises at 61C
MB temperature at 40C

I noticed something funny: After running for a long while, the khash/sec went down to 1750-1800. Is this normal? I see the same thing happening on my laptop where it went down to 275 after staying at 300 - 310 for a while.

Here is my set up.

Windows 7 64-bit
Intel Core 2 Duo P7450
2 cores
2.13 GHz
3 GB RAM
749 khashs/sec

Ubuntu 10.04
AMD Phenom II X4 920
4 cores
2.8 GHz
8 GB RAM
2718 khashs/sec
the bitcoin process runs on all cores but is "niced" to yield cycles to ordinary processes

Hello everyone, first post here.  Currently only have bitcoin running on my eee-1000 but after I upgrade my desktop I will have a node running there as well.  My eee is running:

intel atom N270 1.6 GHZ dual core.
1.0 GB of ram, about 3/4 of which is free/cache under normal operations.
currently getting between 160 and 180 khash's per second with both cores running.

-Buck

Yes, that's the problem.  Microsoft's para-virtualization support for Linux is minimal.  It supposedly works for Red Hat and Debian () but I've had no joy with Ubuntu.

Perhaps I'll set up some Red Hat VMs.  There's another project that needs a virtual network of Red Hat VMs.

Or perhaps Win XP VMs, if I can dig up enough full-install packages.

Thanks, all, for your help.

I'm sorry. It could very well be that your hyper-v is running linux in full-virtualization mode (full is bad). If you ran the client OS in para-virtualization mode, then it would run near full speed. I am not sure if hyper-v supports that or what. Linux is happy to run in para-virtualization mode, so most VM systems can do that just fine.

Hyper-v is a microsoft product. That is your answer. It runs windows fine I'm sure, but it is your problem, not VM technology itself.

For example, I run bitcoin under Xen (linux/linux) and get khash/sec numbers that run with any I've seen posted.

Theoretically, I wouldn't think VM would affect bitcoin performance (coin mining at least) more than maybe a minute amount. The hashing code has zero system calls that need to be passed outside the virtual host, there is no overhead, especially in any good VM system like Xen that utilizes Thread Local Storage, Etc...

(not saying Xen is the best, only that bitcoin should run undetectably less good inside a VM as out; it does for me.)

What's the VM bottleneck for Bitcoin?  Is it CPU virtualization?

Ubuntu on Hyper-V is particularly slow, I admit.  Win 7 x64, OTOH, screams.  Damn.

Wouldn't it suck if NSA (or Google) cornered Bitcoin market?

Why would we want to slow Bitcoin down?
No see, Virtual Machines can cause quite some overhead. And Bitcoin can really use all the resources it can get to generate higher.
As with any computer program, or even any real world system, everything is based around bottlenecks.

The slowest part in a machine determines the actual speed.

More on that here: http://en.wikipedia.org/wiki/Bottleneck

Why is bitcoin so slow on VMs?  Is it intentional, to prevent corporate/government cornering?  Or

Edit: 

Ubuntu 10.04 Server x64
Gateway DX4710
Intel Core2 Quad Q6600
5.5GB real memory
4 CPUs
2,472 khash/s

My mini-cluster of Intel(R) Core(TM)2 Quad CPU Q8400 on FreeBSD 8.0/amd64

hashmeter   32 CPUs   20,704 khash/s

(2588 khash/s per node!! GO TEAM FREEBSD! Roast those penguins! )