Bitcoin Forum
May 11, 2024, 09:05:24 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 [2] 3 4 »  All
  Print  
Author Topic: Post Your Hash/Sec and Hardware  (Read 39002 times)
ichi
Member
**
Offline Offline

Activity: 182
Merit: 10


View Profile
July 12, 2010, 02:11:20 AM
 #21

Hello, all  Smiley  I'm new to Bitcoin.  I'm running client on Ubuntu 10.04 x86 VM with two CPUs and 2.5GB memory.  The VM's running in Hyper-V on Windows Server 2008 x64, on old Dell SC1435 with Quad-Core AMD Operon 2376 and 8BG memory.

It's been up for two days, has 15 connections, and currently sees 65,564 blocks.  This morning, it generated "50", and tells me that they'll mature in 9 more blocks.  That seems more-or-less normal, yes?

What's odd is that it's running at 300-500 khash/s when otherwise idle, but is using only about 1% host CPU on average, with occasional bursts to 10%-20%.  The bursts seem to correlate with disk and network activity, which makes sense.

Anyway, I'm curious why I'm not seeing higher khash/s, given that there's plenty of resources available.

Could it be because the VM is running without Linux integration services (which I haven't managed to install successfully)?  Or could it be because I'm not port forwarding?  And FWIW, I can't do that because I'm connecting through OpenVPN.

How can I increase resource utilization?  Alternatively, I'm sure that Ubuntu would be happy with one CPU and 1GB memory.  Would running four such VMs be workable?

Thank you.  This is fun.
1715418324
Hero Member
*
Offline Offline

Posts: 1715418324

View Profile Personal Message (Offline)

Ignore
1715418324
Reply with quote  #2

1715418324
Report to moderator
1715418324
Hero Member
*
Offline Offline

Posts: 1715418324

View Profile Personal Message (Offline)

Ignore
1715418324
Reply with quote  #2

1715418324
Report to moderator
If you see garbage posts (off-topic, trolling, spam, no point, etc.), use the "report to moderator" links. All reports are investigated, though you will rarely be contacted about your reports.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Xunie
Full Member
***
Offline Offline

Activity: 132
Merit: 101



View Profile
July 12, 2010, 02:16:25 AM
 #22

Hello, all  Smiley  I'm new to Bitcoin.  I'm running client on Ubuntu 10.04 x86 VM with two CPUs and 2.5GB memory.  The VM's running in Hyper-V on Windows Server 2008 x64, on old Dell SC1435 with Quad-Core AMD Operon 2376 and 8BG memory.

It's been up for two days, has 15 connections, and currently sees 65,564 blocks.  This morning, it generated "50", and tells me that they'll mature in 9 more blocks.  That seems more-or-less normal, yes?

What's odd is that it's running at 300-500 khash/s when otherwise idle, but is using only about 1% host CPU on average, with occasional bursts to 10%-20%.  The bursts seem to correlate with disk and network activity, which makes sense.

Anyway, I'm curious why I'm not seeing higher khash/s, given that there's plenty of resources available.

Could it be because the VM is running without Linux integration services (which I haven't managed to install successfully)?  Or could it be because I'm not port forwarding?  And FWIW, I can't do that because I'm connecting through OpenVPN.

How can I increase resource utilization?  Alternatively, I'm sure that Ubuntu would be happy with one CPU and 1GB memory.  Would running four such VMs be workable?

Thank you.  This is fun.


Well, running Bitcoin in an VM slows it down, significantly.
It's better to run it directly on the host operating system.
I suggest you do that.

Ignore this: 734d417914faa443d74e8205f639dfb0f79fdc44988ecae44db31e5636525afe

Caffeinism -- a toxic condition caused by excessive ingestion of coffee and other caffeine-containing beverage.
ichi
Member
**
Offline Offline

Activity: 182
Merit: 10


View Profile
July 12, 2010, 02:27:44 AM
 #23

Thanks, Xunie.  The host isn't secure, for many reasons (MS knows me well, basically).  The VM is running encrypted filesystem, and connects via private VPN.

I'm also playing with Ubuntu 10.04 Server on old gaming machine.  I just need to figure out command line access, because there's no GUI.
robcontact
Newbie
*
Offline Offline

Activity: 1
Merit: 0


View Profile
July 12, 2010, 11:18:49 AM
Last edit: July 12, 2010, 11:45:00 AM by robcontact
 #24

With the default build (Linux x86_64)

Desktop (Xeon x3350 @ 3.2Ghz, 4GB RAM):

4 cores - ~ 3300 khash/s

Laptop (ASUS w/ Core2 Quad Q9000 @ 2GHz):

4 cores - ~ 2000 khash/s


The Madhatter
Hero Member
*****
Offline Offline

Activity: 490
Merit: 509


My avatar pic says it all


View Profile
July 12, 2010, 12:05:34 PM
 #25

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! Tongue )
ichi
Member
**
Offline Offline

Activity: 182
Merit: 10


View Profile
July 12, 2010, 05:16:32 PM
Last edit: July 12, 2010, 05:32:54 PM by ichi
 #26

Well, running Bitcoin in an VM slows it down, significantly.
It's better to run it directly on the host operating system.
I suggest you do that.
Why is bitcoin so slow on VMs?  Is it intentional, to prevent corporate/government cornering?  Or Huh

Edit: 

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

Activity: 132
Merit: 101



View Profile
July 12, 2010, 05:21:50 PM
 #27

Well, running Bitcoin in an VM slows it down, significantly.
It's better to run it directly on the host operating system.
I suggest you do that.
Why is bitcoin so slow on VMs?  Is it intentional, to prevent corporate/government cornering?  Or Huh

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

Ignore this: 734d417914faa443d74e8205f639dfb0f79fdc44988ecae44db31e5636525afe

Caffeinism -- a toxic condition caused by excessive ingestion of coffee and other caffeine-containing beverage.
ichi
Member
**
Offline Offline

Activity: 182
Merit: 10


View Profile
July 12, 2010, 05:34:37 PM
 #28

Why would we want to slow Bitcoin down?
Wouldn't it suck if NSA (or Google) cornered Bitcoin market?
ichi
Member
**
Offline Offline

Activity: 182
Merit: 10


View Profile
July 12, 2010, 05:41:13 PM
 #29

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.
thufir
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
July 12, 2010, 06:15:10 PM
 #30

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.)
thufir
Newbie
*
Offline Offline

Activity: 14
Merit: 0


View Profile
July 12, 2010, 06:21:12 PM
 #31

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.
ichi
Member
**
Offline Offline

Activity: 182
Merit: 10


View Profile
July 12, 2010, 10:00:48 PM
 #32

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.
Yes, that's the problem.  Microsoft's para-virtualization support for Linux is minimal.  It supposedly works for Red Hat and Debian (Huh) 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.
AndrewBuck
Member
**
Offline Offline

Activity: 123
Merit: 15


View Profile
July 13, 2010, 06:38:02 AM
 #33

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
SlipperySlope
Hero Member
*****
Offline Offline

Activity: 686
Merit: 501

Stephen Reed


View Profile
July 13, 2010, 08:14:23 AM
 #34

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

Stone Man
Newbie
*
Offline Offline

Activity: 28
Merit: 8


View Profile
July 14, 2010, 08:09:04 AM
 #35

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
Bitcoiner
Member
**
Offline Offline

Activity: 70
Merit: 11


View Profile
July 14, 2010, 08:55:19 AM
 #36

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.

Want to thank me for this post? Donate here! Flip your coins over to: 13Cq8AmdrqewatRxEyU2xNuMvegbaLCvEe  Smiley
sgtstein
Member
**
Offline Offline

Activity: 61
Merit: 10


View Profile
July 14, 2010, 02:28:02 PM
 #37

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
lobo235
Newbie
*
Offline Offline

Activity: 4
Merit: 0


View Profile
July 14, 2010, 03:41:18 PM
 #38

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.
aceat64
Full Member
***
Offline Offline

Activity: 307
Merit: 102



View Profile
July 14, 2010, 06:55:14 PM
 #39

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.
Bitcoiner
Member
**
Offline Offline

Activity: 70
Merit: 11


View Profile
July 15, 2010, 02:50:35 AM
 #40

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.

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.

Want to thank me for this post? Donate here! Flip your coins over to: 13Cq8AmdrqewatRxEyU2xNuMvegbaLCvEe  Smiley
Pages: « 1 [2] 3 4 »  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!