Ufasoft Miner - Windows/Linux, x86/x64, SSE2/OpenCL, Open Source

[theGECK]

When using your program on another computer, it comes back with 0Mhash/s. When using the generator in bitcoin, or another CPU miner, I get between 400-800khash/s, or .8Mhash/s. This computer has an Intel Core Duo (not Core2) T2050 @ 1.6Ghz.

I sent .5 BTC your way ufasoft, thank you very much for your program - it's helping me out on at least one other computer!

[1714611585]

1714611585

[1714611585]

1714611585

[Ricochet]

If you're getting 0 Mhash, make sure you've got the full URL (including port number) and that the username and password are spelled correctly including correct capitalization for both.  Also with slush's pool make sure you're using two different workers for your two instances of the miner.

This is really interesting.  While with jgarzik's CPU miner I can get just about 1 Mhash/s per core, with this one I'm getting closer to 2.2 Mhash/s per core.  This is on a Core 2 Duo T9300 @2.5 GHz.  I have not compared to any other 4way miner though for comparison.

[theGECK]

Thanks for the advice here. I had the URL as http://mining.bitcoin.cz:8332, when it needed to be http://mining.bitcoin.cz:8332/. Getting .7-.75Mhash/s.

[theGECK]

Feature Request: a timestamp for an accepted string. It's nice to be able to look back and see what my average time was between solutions.

Is the MHash/s rate that displays on an Accepted the average for that acceptance, or the hash rate at the instant it was solved?

[ufasoft]

Is the MHash/s rate that displays on an Accepted the average for that acceptance, or the hash rate at the instant it was solved?

At the instant it was solved. "Rate" here is just last printed line, because after sending solution to server the NewLine character printed.

[ufasoft]

Feature Request: a timestamp for an accepted string. 

Implemented

[theGECK]

Feature Request: a timestamp for an accepted string. 

Implemented

FYI, I downloaded the newest version (Windows .exe) from the link at the head of this topic. No timestamp appears. This is the result I get:

bitcoin-miner 0.1  Copyright <c> 2011 Ufasoft http://ufasoft.com/open/bitcoin
2 threads         Using SSE2
5.88 MHash/s     Result FOUND: EED1711LKJASNX>?<>?<#@*(yBLAH BLAH BLAH
5.7 MHash/s                Accepted
5.84 MHash/s [<--live update of hash speed]

[ufasoft]

FYI, I downloaded the newest version (Windows .exe) from the link at the head of this topic. No timestamp appears. This is the result I get:

It should be version 0.3. Probably your browser cache gives you old file.

[theGECK]

FYI, I downloaded the newest version (Windows .exe) from the link at the head of this topic. No timestamp appears. This is the result I get:

It should be version 0.3. Probably your browser cache gives you old file.

Actually, I had the file in two different locations without realizing it, and was launching the wrong file. The correct one I had put in my "Bitcoin Mining" folder, but when I first tried out the program and created the .bat file to easily launch it, I had put it in a generic "New Folder". Since the .bat was still pointing there and I hadn't remembered the folder existed, I was launching the old version of the miner.

Problem solved, and my "average" performance based on eyeballing the numbers for a few seconds has increased again, with less variance when doing other tasks, from 5.5MHash/s to 6.5MHash/s. I'm liking this miner more and more.

[Cerebrum]

By the way, which libraries are you using? The <ext.h> and the <../libext/ext-http.h> are creating problems for me when trying to compile, and after some googling I still can't figure out where these libraries are coming from. I also don't have definitions for a large number of the classes referenced, so I'm guessing that there is some dependency that is missing here. I'm using Visual Studio 2010 as my Windows build environment.

[ufasoft]

By the way, which libraries are you using?

Our own libs. All necessary Sources of libraries you can find at http://ufasoft.com/files/ufasoft_lisp-4.30.tar.lzma
It is other project, but uses the same framework.

Additionally: bitcoin-miner uses BigInteger to compare with target. Really it is not necessary, memcmp() function is enough

[Cerebrum]

OK, so... your framework is not compiling for me. It seems to be looking for POSIX-style headers on a windows machine. The whole thing is a massive mess of ifdefs, and I have no idea what the actual problem is. Thanks for your help, but unfortunately it looks like I'll try to use your code as a guide to re-implement it as part of jgarzik's miner instead of trying to build it myself.

[ufasoft]

Thanks for your help, but unfortunately it looks like I'll try to use your code as a guide to re-implement it as part of jgarzik's miner instead of trying to build it myself.

That is the best way. BTW I have reimplemented entire SHA-256 SSE algorithm on Assembly Language. It saves at least 10% cycles. So I think you need only this .asm module.

[Mythoranium]

This is, IMHO, an amazing miner! Will definitely donate something.
Haven't looked at the source, but judging by the last post, you are using assembler for the calculations, right? Or is it a different project or future feature?

[Cerebrum]

That is the best way. BTW I have reimplemented entire SHA-256 SSE algorithm on Assembly Language. It saves at least 10% cycles. So I think you need only this .asm module.

Wow, that would be great. Any chance you could post the module?

[ufasoft]

Wow, that would be great. Any chance you could post the module?

.asm added:
http://ufasoft.com/files/open/bitcoin-miner.zip

[xenon481]

I downloaded the latest Windows binary and am getting 10-12% improvement in speed over the previous version. One thing, though, is that the version number inside of the file is the same as the old one.

[Cerebrum]

OK, so... this miner is great! Thank you for all of your help in getting me to understand the basics of how it works. However, I have a few feature requests that I think could help it out:

-Make the delay between work requests settable by the user through the command line instead of it being set statically at 30 seconds as it is now. This would allow the period to be decreased and prevent the unaccepted work problems that I've been having in slush's pool while using this miner.

-Make different levels of output verbosity so that the program doesn't have to throw out a huge amount of hex into the terminal. This is obviously mostly cosmetic, but it would be nice.

[theGECK]

While helping my friend setup this miner, I saw that a new version had been released. 0.3.1. I went from 6.8Mhash to 7.2Mhash maximum.

My friend went from 3Mhash with the first miner he tried to 12Mhash with this one. I have gone from 2Mhash maximum to 7Mhash. Thank you very much.

[Raulo]

Anybody succeeded porting it to Linux? I have no success so far.