Topic: [XPM] Primecoin Built-in Miner Sieve Performance Issue - page 28. (Read 69167 times)
since I started mining with release5.zip about 6 hours ago I have found 4 blocks with 2 i7's at average speeds of 940 and 840 pps.
ok, hopefully the karmic universe will throw something back my way for this. Here is the windows qt-client I built with the new code checked in by Sunny King/
Thanks this worked great for me once I hunted down mingwm10.dll. Another 2 blocks found overnight which is more than usual. I usually get 3 together during the daytime only.
Max PPS up to about 316 from about 250 previously.
Can we get more feedback. Which release is the best so far?
Could be the 32-bit windows, as I am running x64. Maybe a -m32 switch is needed during the compile to force it into 32-bit mode.
right. my i5 and zeon boxes are 64bit win7
Here's one more you can try. Last one from me tonight.
This one has -mtune=i686 -m32, so hopefully it will cross compile to 32-bit OSes. Still runs on my 64-bit one.https://www.dropbox.com/s/uvgn1bcso6sppd0/release7_tuned_for_i686_32-bit.zip
I find I made a mistake. The problem was not the primecoin-qt.exe file was not executable. Rahter both 6 and 7 versions run, but crash after the splash screen, when loading the blockchain.
Could be the 32-bit windows, as I am running x64. Maybe a -m32 switch is needed during the compile to force it into 32-bit mode.
right. my i5 and zeon boxes are 64bit win7
Here's one more you can try. Last one from me tonight.
This one has -mtune=i686 -m32, so hopefully it will cross compile to 32-bit OSes. Still runs on my 64-bit one.https://www.dropbox.com/s/uvgn1bcso6sppd0/release7_tuned_for_i686_32-bit.zip
Were tested all versions of updated client. APPCRASH on all versions of windows (W7 embedded standart x32, w7 home basic x32, w7 proffessional x64, w8 proffesional x64) with 2 core processors celeron, sempron, athlon x2 and 6core phenom x6. Works only on quad core: i5 and athlon X4 works well.
Could be the 32-bit windows, as I am running x64. Maybe a -m32 switch is needed during the compile to force it into 32-bit mode.
right. my i5 and zeon boxes are 64bit win7
Here's one more you can try. Last one from me tonight.
This one has -mtune=i686 -m32, so hopefully it will cross compile to 32-bit OSes. Still runs on my 64-bit one.https://www.dropbox.com/s/uvgn1bcso6sppd0/release7_tuned_for_i686_32-bit.zip
Is primepersec same as what you guys are saying is PPS ?
If yes then I'm doing 1700 to 2000 on my PC.
Which PC is that? That's a lot.If yes then I'm doing 1700 to 2000 on my PC.
(I've got about 510 with the update today)
3930K at 4.7Ghz
I crashed at 4.8ghz after about a hour. Even though I was stable with prime95 27.7 for hours. So not sure why, but this might me my new stability tester.
I have mined for 2 hours with no blocks though.
I still don't know if those numbers are what I should be looking at but by the way you asked a question in replying to my quesiton "Is primepersec same as what you guys are saying is PPS ?"
I assume the answer is yes
primepersec = PPS
?
I see.. the block count is indeed going up. Alright, yeah we will see how it looks by tomorrow.
Are you mining any blocks yourself? I have 1 pending immature that was included with your 4th release and now 5th release, not a single new addition.
The PPS is not a problem.. however, the latest 'non-crash' release seems to be doing worse in blocks mined.
I am running my release 5. I have not gotten a block with it yet, but my luck has been pretty terrible with solo mining, so I'm not surprised. It's definitely "hashing" and keeping up with the blockchain. I'll let it run overnight, more than likely I'll hit at least 1 block before I wake up.
Make sure you current block number is incrementing, I had a build or two that were having problems with that. As long as the blockcount is ticking away, I think you're fine.
FYI, my builds include SOME of the optimizations posted by Mike270 here: https://bitcointalksearch.org/topic/m.2700874
Namely, items 1,2,3,5 from his list.
Could be the 32-bit windows, as I am running x64. Maybe a -m32 switch is needed during the compile to force it into 32-bit mode.
Are you mining any blocks yourself? I have 1 pending immature that was included with your 4th release and now 5th release, not a single new addition.
The PPS is not a problem.. however, the latest 'non-crash' release seems to be doing worse in blocks mined.
I am running my release 5. I have not gotten a block with it yet, but my luck has been pretty terrible with solo mining, so I'm not surprised. It's definitely "hashing" and keeping up with the blockchain. I'll let it run overnight, more than likely I'll hit at least 1 block before I wake up.
Make sure you current block number is incrementing, I had a build or two that were having problems with that. As long as the blockcount is ticking away, I think you're fine.
FYI, my builds include SOME of the optimizations posted by Mike270 here: https://bitcointalksearch.org/topic/m.2700874
Namely, items 1,2,3,5 from his list.
Could be the 32-bit windows, as I am running x64. Maybe a -m32 switch is needed during the compile to force it into 32-bit mode.
Are you mining any blocks yourself? I have 1 pending immature that was included with your 4th release and now 5th release, not a single new addition.
The PPS is not a problem.. however, the latest 'non-crash' release seems to be doing worse in blocks mined.
I am running my release 5. I have not gotten a block with it yet, but my luck has been pretty terrible with solo mining, so I'm not surprised. It's definitely "hashing" and keeping up with the blockchain. I'll let it run overnight, more than likely I'll hit at least 1 block before I wake up.
Make sure you current block number is incrementing, I had a build or two that were having problems with that. As long as the blockcount is ticking away, I think you're fine.
FYI, my builds include SOME of the optimizations posted by Mike270 here: https://bitcointalksearch.org/topic/m.2700874
Namely, items 1,2,3,5 from his list.
Could be the 32-bit windows, as I am running x64. Maybe a -m32 switch is needed during the compile to force it into 32-bit mode.
Are you mining any blocks yourself? I have 1 pending immature that was included with your 4th release and now 5th release, not a single new addition.
The PPS is not a problem.. however, the latest 'non-crash' release seems to be doing worse in blocks mined.
Zalfrin, weird, but all your releases except the 1st one crash upon launch (fail to launch) for me... Win7 64 on i5 (M560) here...
Odd. I guess I don't have much of a future as a releaser of QT files.
If I were you I might try anonppcoin's version. Or hold out for Sunny to put out an official binary. 
Is primepersec same as what you guys are saying is PPS ?
If yes then I'm doing 1700 to 2000 on my PC.
Which PC is that? That's a lot.If yes then I'm doing 1700 to 2000 on my PC.
(I've got about 510 with the update today)
Zalfrin, weird, but all your releases except the 1st one crash upon launch (fail to launch) for me... Win7 64 on i5 (M560) here...
Could be the 32-bit windows, as I am running x64. Maybe a -m32 switch is needed during the compile to force it into 32-bit mode.
right. my i5 and zeon boxes are 64bit win7
Could be the 32-bit windows, as I am running x64. Maybe a -m32 switch is needed during the compile to force it into 32-bit mode.
Is this optimized especially for i5 as release3 above or generically optimized? Thanks
edit: it crashes on start on my i7 L620 laptop and doesn't start on my i5 650 desktop. Both machines worked with your original release plus shinkickers dlls.
edit: it crashes on start on my i7 L620 laptop and doesn't start on my i5 650 desktop. Both machines worked with your original release plus shinkickers dlls.
Yes still optimized for i5. Sorry to hear it's not working for you. I can try a -mtune instead of a -march to make it usable across more processors, but that's basically what anonppcoin's build was doing.
Both release 5 and 6 on my i7 (32bit win7) have the same error -- they are not recognized as executable files. I just found this out by running primecoin-qt in a DOS window.
Release 6 runs on my i5 box. (rel 5 didn't)
Heh... that's a new development. It also appears to be broken again, not pulling in new blocks as they come. Last time that was a UPNP problem.
Quote
All right, here's a fixed version. Includes all dlls, shouldn't be crashing on exit, and should be following the blockchain properly. 
https://www.dropbox.com/s/6dwcc5p1koj86vz/release5.zip
https://www.dropbox.com/s/6dwcc5p1koj86vz/release5.zip
Zalfrin, may I ask what was broken? I am working on some optimizations right now and would like to avoid the same (I'm assuming uPnP) problem. I'm about to hang it up for the night but if I find anything that looks promising tomorrow, I'll let you know. I prefer to keep changes public on the board rather than on IRC like we have been doing.
I'm not exactly sure what happened with the upnp and crashing on exit issues. Only thing I can guess is that playing around with the -static flags somehow introduced it. I've backed those out and the problem went away, but I still have to bundle extra dlls with my qts.
Sunny, can you please release updated binaries..
thank you in advance.
Jim
Jump to: