Bitcoin Forum
December 03, 2016, 10:04:35 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Expected behavior of 32-bit bitcoind when running on AMD x64?  (Read 886 times)
Furyan
Full Member
***
Offline Offline

Activity: 175



View Profile
February 21, 2012, 11:59:43 AM
 #1

I just have a quick question... as an experiment I've tried running the stock 32-bit bitcoind binary from bitcoin.org, on a 64-bit windows machine. The block chain at this point has taken well over 24 hours to download and is still not finished (has about 3000 blocks to go).  Typically it takes ~3 hours on my other machines.

The one key piece of information might be that the box is dual-IP.  It has two IP addresses assigned to its NIC.  What's interesting to me about this is that when I do something like "bitcoind getinfo", it takes several minutes to respond.

Is this expected behavior?  I can simply download and recompile the source for 64-bit, I'm just wondering why I'm seeing this. It doesn't seem to be related to open/closed ports. I do see high-ish CPU usage (average ~30%) but I've always seen this on any machine downloading the block chain.  The debug.log file reveals no interesting messages that might suggest why this is taking so long.

Details:

Bitcoind = 0.5.2 beta
server=1

Machine details:
AMD 2.9 GHz Dual Core Athlon 2
OS: Windows Server 2008 R2
4 GB RAM

Input appreciated.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480802675
Hero Member
*
Offline Offline

Posts: 1480802675

View Profile Personal Message (Offline)

Ignore
1480802675
Reply with quote  #2

1480802675
Report to moderator
1480802675
Hero Member
*
Offline Offline

Posts: 1480802675

View Profile Personal Message (Offline)

Ignore
1480802675
Reply with quote  #2

1480802675
Report to moderator
Revalin
Hero Member
*****
Offline Offline

Activity: 728


165YUuQUWhBz3d27iXKxRiazQnjEtJNG9g


View Profile
February 21, 2012, 10:22:02 PM
 #2

32-bit doesn't matter much.  Bitcoind doesn't use a lot of memory.

The long download time is because Bitcoin verifies all transactions (computationally expensive) as it downloads the blockchain.  If you want to skip this you can download the blockchain here: http://eu1.bitcoincharts.com/blockchain/

      War is God's way of teaching Americans geography.  --Ambrose Bierce
Bitcoin is the Devil's way of teaching geeks economics.  --Revalin 165YUuQUWhBz3d27iXKxRiazQnjEtJNG9g
grue
Global Moderator
Legendary
*
Offline Offline

Activity: 1932



View Profile
February 22, 2012, 12:45:55 AM
 #3

It shouldn't matter on windows. syswow64 handles the conversion between the two architectures no problem. If you have lot of ram (over 4 gb), you can try setting bitcoin's data directory to a ram drive. You will be able do download the blockchain in less than 1 hour.

It is pitch black. You are likely to be eaten by a grue.

Tired of annoying signature ads? Ad block for signatures
Furyan
Full Member
***
Offline Offline

Activity: 175



View Profile
February 22, 2012, 05:00:48 PM
 #4

It shouldn't matter on windows. syswow64 handles the conversion between the two architectures no problem. If you have lot of ram (over 4 gb), you can try setting bitcoin's data directory to a ram drive. You will be able do download the blockchain in less than 1 hour.

I'd have thought the same thing, esp. since the machine is on a gigabit network.  Seems the problem was the dual-IP.. it confused the pool server too, so that was probably it.

All fixed now just thought it was odd..
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!