Topic: 0.3 almost ready -- please test the Mac version! - page 2. (Read 25091 times)

Windows 7 x64
4 GB RAM
Intel i7 860

4 cores ( 8 virtuals ): 2200 khash/s

It's lower than Ubuntu :|

I don't know.  Maybe someone with more Linux experience knows how to install the library it needs.

I built it on Ubuntu 10.04.  I hope that wasn't a mistake.  Maybe it should have been built on an older version for more backward compatibility.  Is this a problem on Linux, that if you build on the latest version, then it has trouble working on older versions?  Is there any way I can downgrade to an older version of GCC on 10.04?

The 64-bit version shouldn't be any faster than the 32-bit version, but it would be great if someone could do a side-by-side comparison of the two linux versions and check.  SHA-256 is a 32-bit algorithm and nothing in BitcoinMiner uses 64-bit at all.

We don't need to bother with a 64-bit version for Windows.  32-bit programs work on all versions of Windows.  It's not like Linux where the 64-bit OS wants 64-bit programs.

I'm also curious if it's a little faster on linux than windows.

Do you think I should make the directories:
/bin32/
/bin64/
instead of
/bin/32/
/bin/64/

Ubuntu 9.04 x86:

vlad@vlad:~/bitcoin/bin/32$ ./bitcoind
./bitcoind: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by ./bitcoind)

Anybody know what Bitcoin needs?

will it change something if you release a x64 bit version for Windows?

Nice. :-)

64-bit version works fine on Ubuntu 10.04, of course it's (much) faster than through WINE emulation (and because it's 64-bit!?)

4 cores: 2850 khash/s
3 cores: 2130 khash/s
2 cores: 1420 khash/s
1 core: 700 khash/s

WINE (32-bit):

4 cores - 2300 khash/s
3 cores - 1740 khash/s
2 cores - 1150 khash/s
1 core - 580 khash/s

Thank you - looks pretty nice, too.

http://i50.tinypic.com/2ih1h0p.jpg

edit: What's the difference between "Sent/Received" and "All transactions"?

Here's RC1 for linux for testing:
(link removed, see below)

It contains both 32-bit and 64-bit binaries.

Recent changes:

build-unix.txt:
- Added instructions for building wxBase, which is needed to compile bitcoind.
- The package libboost-dev doesn't install anything anymore, you need to get libboost-all-dev.
- Updated version numbers.

makefile.unix:
- The libboost libraries have removed the "-mt" from their filenames in 1.40.  If you're compiling with Boost 1.38 or lower, like on Ubuntu Karmic, you would need to change it back to boost_system-mt and boost_filesystem-mt.

Much faster than Laszlo's build for me. Went from 600-700khash/s to 1000-1100khash/s on my Intel Core 2 Duo E8500. From 700-800khash/s on a laptop i7 to ~1100khash/s.

edit: Keeping the "Run Bitcoin" option checked in the installer seems to run it with admin privileges on the first launch. (in Win7)

Laszlo figured out that enabling some more optimisation increased performance about 20%, so 0.3 hashes 20% faster than 0.2.0, but I assume he used that in his own build.

30khash increase to what total rate?  (to figure the % increase)

Yeah, 0.3.0 seems to have a performance increase over svn r84 with Laszlo's performance patch.

Runs fine under WINE. *rhymes*

It automatically switched the language to German, too. Now that I can see the translation in the client itself, I noticed a few things to improve, and will post a new .po file within the next two or so days.

yes, I'm just using 0.30 by now.
Thank you!

You figured it out faster than I could post a reply.  

It looks like laszlo's build of Berkeley DB has database/log.* files that are not compatible with ours.  The .dat files are fine, their format shouldn't ever change.  All data is stored in the .dat files.  All your own data is stored in wallet.dat.  If you had waited for it to redownload the block chain, your missing transactions and generateds would have appeared as the block chain reached the point where those transactions were recorded.

When you copied the directory except log.0000000002, that's the best solution.  You should be good now.

The database/log.* files only contain temporary database data.  If you exited bitcoin normally the last time, not exited by forced terminating it or crashing, then the database/log.* files can normally be deleted safely.  They're only used so that if the database is in the middle of a transaction when the computer crashes or the program is killed or crashes, then it could recover without losing data.

Please keep running v0.3 if at all possible, don't go back to v0.2.10.

Anyone else who hits this problem, move the database\log.000000000* files somewhere else.  (if it works fine after that, you can delete them later)

I'm reluctant to make the installer delete or move those files.  If the previous run was stopped by crashing or killed, that would be the wrong thing to do.

Both are existing

Yes it works.

so I closed it, copied the walled.dat from the old folder to the new one, and now it's downloading blocks
Address book and old transfers seem ok, but there aren't anyone of old "generated coins" ... I just need to wait?
Anyway, I can just go back with the old v0.2.10

EDIT:
I did another thing.
Closed it, copied addr.dat / blk0001.dat / blkindex.dat from old folder to the new one.
Restarted bitcoin ( v0.30 ), and now it seems that everything is working. ( I can see also old generated coins now )
I just did NOT copied "log.0000000002" from the database folder ...

davidonpda, were you also running laszlo's build previously?

Check if the "%appdata%" directory exists, and "%appdata%\bitcoin"

Try:
 rename "%appdata%\bitcoin" bitcoin2

does it work then?

Windows 7 x64 ENG
4 GB RAM
Intel i7 860

I was using the v0.2.10 build by laszlo before yours.

What operating system?

Normally when it does that it's because the directory where the data directory should go doesn't exist.  See if the "%appdata%" directory exists.

Do you get that error with 0.2 also?  It's hard to see how you could get that with 0.3 and not with 0.2 since there's nothing different in that regard.

I have the same problem :|

I just finished creating a clean Amazon EC2 debian 5.0 machine image with everything I needed to compile bitcoind, and it compiled (using a variation of Laszlo's makefile.unix) and is running fine (just finished downloading the block chain).  I'll let you know if it misbehaves.

I had trouble compiling the gtk version, but I think that's because I did something wrong compiling wxWidgets.  I don't need no stinkin' graphics (and am not a wxWidgets expert), so I'm not going to bother trying to fix that.

Here's RC1 for windows for testing:
(removed, see RC2 below)

Please only download this if you're going to test and report back whether everything seems fine or not.  Make sure to look through the files in "c:\program files\bitcoin"

My fear is too many programmers would latch onto that for checking for received payments.  It can never be reliable that way.  The list/getreceivedbyaddress/label functions are the only way to do it reliably.

We shouldn't delay forever until every possible feature is done.  There's always going to be one more thing to do.