Author

Topic: [XPM] [ANN] Primecoin Release - First Scientific Computing Cryptocurrency - page 119. (Read 688812 times)

sr. member
Activity: 401
Merit: 250
just a warning, when I tried compiling on VS2012 with optimizations, I found that my serialization code was off kilt, and run into all sorts of issues...

if you're playing with the reference client, it might be worth just trying to optimize prime.c (via CFLAGS override in Makefile) since that's where all the logic for calculations are - and you won't risk messing with any of the other important network code.

Will

Probably a good idea, testing with -O3 only on prime.
legendary
Activity: 1470
Merit: 1021
How do we get on the right chain?

Looks like some of the custom builds were causing these issues.
legendary
Activity: 1470
Merit: 1021
Nobody noticed Vircurex just added XPM?

They went down shortly after that, but now they are fine and dandy again Wink


Looks like coins-e was abandoned because of this  Tongue
legendary
Activity: 1470
Merit: 1021
How long does it usually take for a transaction to appear in your wallet?
I sent 2 separate transactions over 2 hours ago and still nothing Sad any idea?

Did you add .01 tx fee in your wallet settings?
member
Activity: 81
Merit: 1002
It was only the wind.

Who knows, it could be a 1000x speedup. I would be careful before saying it's rubbish. Compile and see.

he means "i lack the knowledge to do anything like that, so liek you dont give me free mining so liek lol.. (idiocracy was a great movie, still watching it time to time to remind me what kind of society we are going for)...
Really? That makes no sense. I just don't wanna bother compiling, my VS 2012 hasn't been used for a while.
Then you "don't wanna bother" getting the latest updates, which could include speedups.
full member
Activity: 224
Merit: 100
That was incredibly strange, 17754 was taking a long long time it seemed.  All of a sudden the block solve rate just slowed tremendously from a glance at the block count.  It went from one every 10 seconds to 20-30 seconds plus.
hero member
Activity: 767
Merit: 500
just a warning, when I tried compiling on VS2012 with optimizations, I found that my serialization code was off kilt, and run into all sorts of issues...

if you're playing with the reference client, it might be worth just trying to optimize prime.c (via CFLAGS override in Makefile) since that's where all the logic for calculations are - and you won't risk messing with any of the other important network code.

Will
full member
Activity: 224
Merit: 100
I am starting to get orphan city using the a compiled build from github....Something must have happened, maybe optimized miners out now or GPUs being used.  It seems a bit fishy.
member
Activity: 81
Merit: 1002
It was only the wind.

Who knows, it could be a 1000x speedup. I would be careful before saying it's rubbish. Compile and see.

he means "i lack the knowledge to do anything like that, so liek you dont give me free mining so liek lol.. (idiocracy was a great movie, still watching it time to time to remind me what kind of society we are going for)...

Well, if he lacks the knowledge, he better go get it, because no one's going to cater to him.
newbie
Activity: 50
Merit: 0
Just the processor architecture that the compiler optimized the code for. 11 might be faster but won't run on as many processors. 12 should be more widely supported, it's a more generic instruction set.

Your initial release is solid, and I've mined a few blocks with it. I haven't noticed any blockchain issues on any of my machines.


Even so, I'd recommend switching over to one of these new versions. Primespersec look to be about the same, and there's definitely something to be said for being on the official codebase versus the code I hacked together based on some optimization suggestions. That was actually done before Sunny released his sieve code update, which made the most difference by far anyways.

I should have been more specific. I'm using a build with the updates from Sunny. That update translated into 4x the speed.
sr. member
Activity: 401
Merit: 250
Just the processor architecture that the compiler optimized the code for. 11 might be faster but won't run on as many processors. 12 should be more widely supported, it's a more generic instruction set.

Your initial release is solid, and I've mined a few blocks with it. I haven't noticed any blockchain issues on any of my machines.


Even so, I'd recommend switching over to one of these new versions. Primespersec look to be about the same, and there's definitely something to be said for being on the official codebase versus the code I hacked together based on some optimization suggestions. That was actually done before Sunny released his sieve code update, which made the most difference by far anyways.
newbie
Activity: 50
Merit: 0
Just the processor architecture that the compiler optimized the code for. 11 might be faster but won't run on as many processors. 12 should be more widely supported, it's a more generic instruction set.

Your initial release is solid, and I've mined a few blocks with it. I haven't noticed any blockchain issues on any of my machines. I have a Sandy Bridge CPU working phenomenally with your i5 optimized build. The rest are using your first build. I don't know if I'm unlucky, but I've rebooted all of the machines that haven't found a block in a few hours.
sr. member
Activity: 401
Merit: 250
Please download updated clients, these are using the official code base versus the "optimized" code on my branch which may be causing problems.

These replace my releases 5 and 8 respectively. Let me know if there are any other releases you were using.

https://www.dropbox.com/s/76eij0zcjx091am/release11_sandybridge_i5.zip
https://www.dropbox.com/s/lxm220qqztpgps5/release12_x86-64.zip


Thanks, what's the main differences between the two above?

Just the processor architecture that the compiler optimized the code for. 11 might be faster but won't run on as many processors. 12 should be more widely supported, it's a more generic instruction set.
member
Activity: 81
Merit: 1002
It was only the wind.

Who knows, it could be a 1000x speedup. I would be careful before saying it's rubbish. Compile and see.
sr. member
Activity: 401
Merit: 250
Anyone have an i5 haswell optimized windows binary? I'll shoot you some XPM.

I would probably try the x86-64 build (12), unless you see something on this list that is closer: http://gcc.gnu.org/onlinedocs/gcc/i386-and-x86_002d64-Options.html
sr. member
Activity: 266
Merit: 251
Please download updated clients, these are using the official code base versus the "optimized" code on my branch which may be causing problems.

These replace my releases 5 and 8 respectively. Let me know if there are any other releases you were using.

https://www.dropbox.com/s/76eij0zcjx091am/release11_sandybridge_i5.zip
https://www.dropbox.com/s/lxm220qqztpgps5/release12_x86-64.zip


Thanks, what's the main differences between the two above?
member
Activity: 103
Merit: 10
Anyone have an i5 haswell optimized windows binary? I'll shoot you some XPM.
sr. member
Activity: 401
Merit: 250
Please download updated clients, these are using the official code base versus the "optimized" code on my branch which may be causing problems.

These replace my releases 5 and 8 respectively. Let me know if there are any other releases you were using.

https://www.dropbox.com/s/76eij0zcjx091am/release11_sandybridge_i5.zip
https://www.dropbox.com/s/lxm220qqztpgps5/release12_x86-64.zip
hero member
Activity: 616
Merit: 500
There is no Block from last 24 hours......... What happened?
a: you got disconnected
b: your on the wrong chain
c: you chain updates stopped for some reason

I am online.....

How to solve these other issues?
member
Activity: 81
Merit: 1002
It was only the wind.
Jump to: