Pages:
Author

Topic: [ANN] MemoryCoin - page 25. (Read 100338 times)

legendary
Activity: 1428
Merit: 1030
August 13, 2013, 11:26:49 PM
All 3 my machines went down at block 2060 so it looks as if there are still some problems with grant-block processing.
As I mentioned before, once the problem is solved that you can load the blockchain while mining, this will prove the client is stable enough to run without crashing.

Okay, that sounds like stability issue 1 . . . it's weird that you'd be seeing problems on all your machines, when many others don't have any stability problem . . . I wonder what might be common to all three machines.

I'm assuming these aren't hard machine crashes, as you know which block you're going down on. It would be helpful to get the tail end of the debug.log file after a crash . . it will probably have crashed somewhere in the middle of the grant allocation code, and then there will be some superfluous network activity . . . just before the network activity is where the interesting stuff is.
full member
Activity: 217
Merit: 100
August 13, 2013, 05:27:01 PM
The good news is I am also seeing improved mining performance.

 Smiley
full member
Activity: 217
Merit: 100
August 13, 2013, 04:47:02 PM
Running the latest code, I was getting a SEGFAULT on start up (whilst checking the Genesis block).

I had to revert PoWHash() to the original scrypt() call to get it to work. PoWHashScratchPad() seems to work fine with the new scryptscratchpad().
sr. member
Activity: 308
Merit: 250
August 13, 2013, 04:13:24 PM
stuck at block 2060 here
sr. member
Activity: 332
Merit: 250
August 13, 2013, 03:52:22 PM
I have been stable for days, the trick for me was to specify using only the amount of real CPU cores you have with genproclimit=# in your memorycoin.conf file.  I have 5 machines running 24x7 now with no issues.

Yes, I read that in your ealier posts and tried that too but it doesn't work for me Sad
On my 6-core i7 the client even crashed when set to use only 3 cores.

It's really strange why all my machines are affected so much while other forum members have no problems at all.
I will try one more thing: close my debug window. I always have this open to see if the miner is still on the right block.
Do you have your debug window open when your machines run stable 24/7 ?
sr. member
Activity: 305
Merit: 250
August 13, 2013, 03:33:47 PM
However it doesn't start at all on my low-end PC, so I'm not going to post it in the main thread yet until I've got that sorted out. Shouldn't be an issue on medium to high end systems though. If it is, please post details about your system.
I can't comment on stability yet since I just installed it on all 3 machines. I have had crashes (many, many times) on all machines before, so I hope I can bring some good news later.

I can comment on stability now: still not very stable Sad
All 3 my machines went down at block 2060 so it looks as if there are still some problems with grant-block processing.
As I mentioned before, once the problem is solved that you can load the blockchain while mining, this will prove the client is stable enough to run without crashing.

I have been stable for days, the trick for me was to specify using only the amount of real CPU cores you have with genproclimit=# in your memorycoin.conf file.  I have 5 machines running 24x7 now with no issues.
sr. member
Activity: 332
Merit: 250
August 13, 2013, 03:30:31 PM
However it doesn't start at all on my low-end PC, so I'm not going to post it in the main thread yet until I've got that sorted out. Shouldn't be an issue on medium to high end systems though. If it is, please post details about your system.
I can't comment on stability yet since I just installed it on all 3 machines. I have had crashes (many, many times) on all machines before, so I hope I can bring some good news later.

I can comment on stability now: still not very stable Sad
All 3 my machines went down at block 2060 so it looks as if there are still some problems with grant-block processing.
As I mentioned before, once the problem is solved that you can load the blockchain while mining, this will prove the client is stable enough to run without crashing.
hero member
Activity: 560
Merit: 500
August 13, 2013, 01:25:36 PM
Getting these numbers on 64bit Windows, i7 6 core Gulftown
I've not had problems on this machine, using "setgenerate true -1"

18:11:43
{
"blocks" : 2048,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00016449,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 21.91060473,
"pooledtx" : 0,
"testnet" : false
}

19:20:05
{
"blocks" : 2056,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00015662,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 23.33268520,
"pooledtx" : 0,
"testnet" : false
}

But on my Windows XP, 32 bit laptop, program crashes after only a few seconds. I've not investigated further, would you like me to try this latest version?
legendary
Activity: 1428
Merit: 1030
August 13, 2013, 12:44:22 PM
win7 32bit

Think 32bit might be the factor with this release. It's working on my 64bit OS, not on 32bit.
sr. member
Activity: 305
Merit: 250
August 13, 2013, 12:31:31 PM
It only works for me if I specify genproclimit=.  If I specify -1 trying to use Hyperthreading, it crashes.

Thanks - and what range of numbers can you specify? Is it only the exact number of cores that works?

I have 4 core Ivy bridge, 8 core Sandy bridge Xeon, and 10 core Ivy Bridge.  Anything over 4 cores and I have to specify or it crashes.
sr. member
Activity: 420
Merit: 250
August 13, 2013, 12:28:34 PM
win7 32bit
hero member
Activity: 695
Merit: 500
August 13, 2013, 11:48:46 AM
Downloaded the newest version and still did not fix the problem Sad
Same message and the blockchain will not download, even thogh I am conectet to the network with 5 active conections...


Hmm - try adding this node by typing,

addnode 180.183.154.90 add

(and wait a few minutes)

Also try starting with re-index, deleting your block directory.

If all that doesn't help, send you debug.log file to [email protected] and I'll look into it.

Hey thanks!
Just re-indexed the block directory and its working again Smiley
sr. member
Activity: 308
Merit: 250
August 13, 2013, 11:09:02 AM
I have a FX-8350 at 4.4Ghz and the newest client starts up and gives me 16.88 hashespersec

64-bit
sr. member
Activity: 332
Merit: 250
August 13, 2013, 10:59:50 AM
However it doesn't start at all on my low-end PC, so I'm not going to post it in the main thread yet until I've got that sorted out. Shouldn't be an issue on medium to high end systems though. If it is, please post details about your system.

I have 3 machines and it starts on all 3 of them.
i7 extreme 6-core, i7 extreme 4-core, 2-core celeron (ivy-bridge).

I can't comment on stability yet since I just installed it on all 3 machines. I have had crashes (many, many times) on all machines before, so I hope I can bring some good news later.

EDIT: Running windows 7 64-bit
legendary
Activity: 1428
Merit: 1030
August 13, 2013, 10:27:01 AM
It only works for me if I specify genproclimit=.  If I specify -1 trying to use Hyperthreading, it crashes.

Thanks - and what range of numbers can you specify? Is it only the exact number of cores that works?
sr. member
Activity: 305
Merit: 250
August 13, 2013, 10:07:35 AM
It only works for me if I specify genproclimit=.  If I specify -1 trying to use Hyperthreading, it crashes.
legendary
Activity: 1428
Merit: 1030
August 13, 2013, 09:45:58 AM
does not work for me (intel core(TM) i5 CPU 660 @3.33Hz 3.33 GHz)

Thanks - what OS and 32bit or 64bit?
member
Activity: 93
Merit: 10
August 13, 2013, 09:45:22 AM
"blocks" : 2021,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00010833,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 16.48464867,
"pooledtx" : 0,
"testnet" : false

"blocks" : 2021,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 0.00010833,
"errors" : "",
"generate" : true,
"genproclimit" : -1,
"hashespersec" : 13.13485114,
"pooledtx" : 0,
"testnet" : false

using i7 870 @ 3.5 MHz here. hashpersec fluctuates between these 2 speeds. an improvement over previous release where it fluctuates between 11 and 14
so about 15%-20% improvement in speeds for me. just to clarify about the stability, i wasn't getting any crashes or problems ever since the first release anyway. so i won't be able to comment on anything about that.
sr. member
Activity: 420
Merit: 250
August 13, 2013, 09:43:20 AM
does not work for me (intel core(TM) i5 CPU 660 @3.33Hz 3.33 GHz)
legendary
Activity: 1428
Merit: 1030
August 13, 2013, 09:20:11 AM
New client - performance and stability improvements.

https://docs.google.com/file/d/0B-5Ax5kejTpMTGJPMTdRZ3V0XzA/edit?usp=sharing

This allocates specific memory for hashing, rather than continually allocating and de-allocating. It gives 15% to 20% performance improvment. It may also improve stability (stability problem 2).

However it doesn't start at all on my low-end PC, so I'm not going to post it in the main thread yet until I've got that sorted out. Shouldn't be an issue on medium to high end systems though. If it is, please post details about your system.

New source at github shortly.
Pages:
Jump to: