[ANN] MemoryCoin | CPU Coin | Paid Dev Team | Limited Supply [MMC]

[reaxion]

I have the new update running but i was using "setgenerate true 6" on my i7 2600 and was getting 2.2 Hpm so i could use work on the pc whilst mining. with the new update i can only use 4 or 8 of my threads and not the 6 which was running at 75% Cpu

4 threads is 50% Cpu @1.5 Hps
8 threads is 100% Cpu @2.6 Hps that is unusable

why have you removed the 6 i though you could go in 2's with how many threads you using ?

[1713438221]

1713438221

[bitcoinxiaoshan]

Have been mining for 24hours+, but nothing found, with a HPM 1.05... How many people are mining?

[badbonez]

Thought I would share my stats to help keep the momentum going

i7-3610QM @ 2.30ghz

"blocks" : 446,
"currentblocksize" : 2779,
"currentblocktx" : 8,
"difficulty" : 0.00001555,
"errors" : "",
"genproclimit" : 8,
"hashespermin" : 2.52846438,
"pooledtx" : 8,
"testnet" : false


I'm happy for an 18 month old laptop

Hmm...I have Intel i7-3820 @ 3.6 GHZ
24GB RAM

{
"blocks" : 565,
"currentblocksize" : 1193,
"currentblocktx" : 1,
"difficulty" : 0.00003196,
"errors" : "",
"genproclimit" : 8,
"hashespermin" : 2.09299892,
"pooledtx" : 1,
"testnet" : false
}

Does this seem right?  Compared to the laptop?  Anything I can do to bump up the h/min?  I tried to setgenerate true 32 but all that does is heat up my CPU, no hash speed increase.  I can overclock, does that help?

Cheers!

[automake]

Thought I would share my stats to help keep the momentum going

i7-3610QM @ 2.30ghz

"blocks" : 446,
"currentblocksize" : 2779,
"currentblocktx" : 8,
"difficulty" : 0.00001555,
"errors" : "",
"genproclimit" : 8,
"hashespermin" : 2.52846438,
"pooledtx" : 8,
"testnet" : false


I'm happy for an 18 month old laptop

Hmm...I have Intel i7-3820 @ 3.6 GHZ
24GB RAM

{
"blocks" : 565,
"currentblocksize" : 1193,
"currentblocktx" : 1,
"difficulty" : 0.00003196,
"errors" : "",
"genproclimit" : 8,
"hashespermin" : 2.09299892,
"pooledtx" : 1,
"testnet" : false
}

Does this seem right?  Compared to the laptop?  Anything I can do to bump up the h/min?  I tried to setgenerate true 32 but all that does is heat up my CPU, no hash speed increase.  I can overclock, does that help?

Cheers!

your hpm is a little low

My I7 3770 4 core 8 thread

{
    "blocks" : 567,
    "currentblocksize" : 1385,
    "currentblocktx" : 2,
    "difficulty" : 0.00002454,
    "errors" : "",
    "genproclimit" : 8,
    "hashespermin" : 3.56588164,
    "pooledtx" : 2,
    "testnet" : false
}

[traxx187]

no block source available on my wallet what gives?

[sid280]

Thought I would share my stats to help keep the momentum going

i7-3610QM @ 2.30ghz

"blocks" : 446,
"currentblocksize" : 2779,
"currentblocktx" : 8,
"difficulty" : 0.00001555,
"errors" : "",
"genproclimit" : 8,
"hashespermin" : 2.52846438,
"pooledtx" : 8,
"testnet" : false


I'm happy for an 18 month old laptop

Hmm...I have Intel i7-3820 @ 3.6 GHZ
24GB RAM

{
"blocks" : 565,
"currentblocksize" : 1193,
"currentblocktx" : 1,
"difficulty" : 0.00003196,
"errors" : "",
"genproclimit" : 8,
"hashespermin" : 2.09299892,
"pooledtx" : 1,
"testnet" : false
}

Does this seem right?  Compared to the laptop?  Anything I can do to bump up the h/min?  I tried to setgenerate true 32 but all that does is heat up my CPU, no hash speed increase.  I can overclock, does that help?

Cheers!

Yer that's weird - I'm using win7 64 bit - client before the fork, maybe that's got something to do with it?

I opened it, went Settings -> Mine with 8 Processes .... and it just worked (Yaaay!)

[badbonez]

I have two quick q's:

1)  I have downloaded and am using the 0.8.53 version and have 3 active connections.  But it's been over 20 minutes and it is still calculating the hash rate.  In addition, when I go to the console and getmininginfo, nothing happens, I get no response.  Is it mining? Any ideas why I can't get the console information?
Did u run "setgenerate true 4" (or 8, 16, 32)? You can check the cpu usage to make sure it hit 99-100%

2) In General, what's the difference between the 4 processes and 8 processes?  Does it affect the hash rate?  8 is faster?  Any reason not to use 8 processes?  (OK, that's 3 questions in one )
The more processe (cpu core) you have the fast mining you will get.

Cheers!

I got things working by deleting the appdata files (except the wallet and blockchain).  When it restarted, it immediately started mining and my hash rate was displayed.  I tried the setgenerate true 32, but that didn't seem to do much more than the 8 processes I am using now.  Might be my CPU...i7 3820 @ 3.6ghz.

Thanks for the assist!

[traxx187]

i got it workikng whoo!!! thanks

[FreeTrade]

I have the new update running but i was using "setgenerate true 6" on my i7 2600 and was getting 2.2 Hpm so i could use work on the pc whilst mining. with the new update i can only use 4 or 8 of my threads and not the 6 which was running at 75% Cpu

4 threads is 50% Cpu @1.5 Hps
8 threads is 100% Cpu @2.6 Hps that is unusable

why have you removed the 6 i though you could go in 2's with how many threads you using ?

Running 6 threads may have looked like it was working, but was likely producing a high proportion of junk. Try running 2 instances together, one at 4 and one at 2 - you'll need 2GB of memory, but should see improved combined hash rate.

[truckythin]

to tired with crashing every 1h   

[NxtChoice]

Mining several hours with 1.01 hashespermin, no block found.

How long will I expect a block with 1.01 hashespermin?

Thanks.

[FreeTrade]

this one: http://www.openssl.org/source/openssl-1.0.1e.tar.gz

Try adding

EVP_cleanup();

at line 136 of momentum.cpp

This might free the memory.

[atlocc]

how can you find target from difficulty?

[radiumsoup]

this one: http://www.openssl.org/source/openssl-1.0.1e.tar.gz

Try adding

EVP_cleanup();

at line 136 of momentum.cpp

This might free the memory.

no effect on Ubuntu 13.10 64bit; using 8.53

[belltown]

that's unnecessary. I've found that the problem is exacerbated by the number of threads being used; perhaps he's only using 2 or 4 cores and therefore hasn't hit a hard limit yet?

I ended up just writing a script to restart the daemon if (when) cpu drops below a certain threshold, indicating the process has crashed... hacky, but good enough for now.

radiumsoup, can you share that script? appriciate

radiumsoup, please post a workaround script, you will help many people.
I'll put a link on www.MemoryCoin.info
Thank you!

[kileris]

recompiled from git, it says i am still on 85200 version, what am I doing wrong?

[Chida]

hi guy,
someone can generate a node at port 80 or 8080 for bypass firewall restriction?
Thanks

[radiumsoup]

that's unnecessary. I've found that the problem is exacerbated by the number of threads being used; perhaps he's only using 2 or 4 cores and therefore hasn't hit a hard limit yet?

I ended up just writing a script to restart the daemon if (when) cpu drops below a certain threshold, indicating the process has crashed... hacky, but good enough for now.

radiumsoup, can you share that script? appriciate

radiumsoup, please post a workaround script, you will help many people.
I'll put a link on www.MemoryCoin.info
Thank you!

sorry, I didn't see that earlier request... what I wrote is highly dependent on my own peculiar setup (resident launch/relaunch script triggered by rc.local, cron job to launch a cpu monitor, and the daemon itself). I can help point people in the direction I took I suppose though. bash script with pseudocode in comments:

Code:

INTERVAL=15; # seconds between cpu checks
THRESHOLD=".6 * $(/usr/bin/nproc)"; # average per-CPU load minimum before we assume it died
while :
do
FIVEMINCPU=($(cat /proc/loadavg | cut -d ' ' -f 2))
if (( $(echo "$FIVEMINCPU" '<' "$THRESHOLD" | bc -l) )); then
#kill any remaining running process using whatever method matches your setup (I used killall -s 9 bitcoind, because the memorycoin executable is the only thing named bitcoind on these hosts)
#launch the daemon again, again depending on your setup (I have it launching automatically from another script if it detects it's not already running)
sleep 600; # must be set to enough time to allow the process to start, scan the blocks, and bring the 5-minute load average back above the threshold.
fi
sleep $INTERVAL;
done

note that you should not run this at boot without first allowing the daemon to launch and start to pull the 5-minute average up, otherwise it will kill the process before it has a chance to peg the cpus. I have this set to launch at boot with a 600 second sleep before the while loop begins.

I know there are a lot of better ways to accomplish the same, but this is just lipstick on the pig until someone who knows C much better than I do (which isn't saying much) can figure out the memory leak, at which point this (hopefully) becomes unnecessary.

[rambobt]

FreeTrade
When YOU fix bugs, crashing linux wallet?

I've install memorycoin client on 4 different linux server and they still to work from three days without problems.

Give some informations about your system, maybe I can try to help you



FaSan

Only your miner work well ,and we are all crash!!!

[trankil]

my sys admin friend found 2 block this night