Got 1 more left, free to the first person, active in alt currency forum, to either pm me your steam email or steam id thing  Andy |
|
|
|
|
Thanks guys, really appreciated.
I think I need to think of a way to make it less-costly. Seeing if it'll work on a AWS instance, instead of a dedi server or putting google-ads up on it.
Obviously if I end up taking it down, I will put the code up before or very shortly after - the code for the patch is already somewhere inside one of the PPC threads.
|
|
|
|
Not received any donations for this website, currently renting a server at 33euro/month.
Will be closing this site probably in next month or so.
 that is very sad i will send u a donation tonight.... though i'm sure I had sent u donation in the past for this site also if you throw me your code i will host it on one of my sites you have my email in ur PM I think I had one ill put the code up somewhere after, it's mostly perl based, and uses the C patch I made for the ppcclient (currently used on the dice site too afaik) |
|
|
|
|
Not received any donations for this website, currently renting a server at 33euro/month.
Will be closing this site probably in next month or so.
|
|
|
|
|
I swear earlier on this thread, I posted a lot of pm's/info about dank, and how he scammed me. Really took 109 pages for people to learn this?
|
|
|
|
|
I have a few free DOTA 2 invites to, drop me a pm.
|
|
|
|
|
Current positions:
Anon 31BTC,
og2k 5BTC.
Will be closing down over next weeks.
Starting from Sun 13th Jan, ill be paying back 10%/week as such payments over next ten weeks are as follows, I *may* choose to close quicker, but, this is the current plan (reserve rights to alter as per op timelines etc)
10 payments of 3.1 on top of weekly interest payments (0.310,0.279,0.248,0.217,0.186,0.155,0.124,0.093,0.062,0.031)
10 payments of 0.5 on top of weekly interest payments (0.05,0.045,0.04,0.035,0.03,0.025,0.02,0.015,0.01,0.005);
I assume Psy will confirm receiving his collat back at some point.
Andy
|
|
|
|
Next week, instead of sending me the interest + 40% of my deposit, please send the full deposit back.
ok Andrew. |
|
|
|
|
Interest paid this week. Been busy with other business recently.
To depositors, will be paying back 40% of deposits next week to interest addresses (along with this upcoming weeks interest on full balances), if anybody wants to change the payout address, pm me new address, signed with interest address. (total deposits will become 36.)
|
|
|
|
|
Investors, as per op mentioned i'd looked to reduce interest after a couple months, I am going to reduce to 1% interest/week week commencing 18/11/12.
Andy
|
|
|
|
|
Sent a few hours early as not around tomorrow day, need to update op with more recent feedback at some point - but not looking for new deposits so no rush. Updating op with cash info thou
|
|
|
|
|
It's defo not sendtoaddress or getmemorypool.
getblockcount is normally used to decide if to throw out a LP, or if cached "getworks" are valid (in some pool software)
im pretty sure, that it's to do with getwork call, when a new block is found.
|
|
|
|
Didnt check if it was proportional to generate or getwork, as, hard to tell which - could even be to "mature", but I observed it as per below, prior to "mature" being reached.
I was running a private pool for a while yes, I could set it up again, but the pool software wasnt the problem - I replicated the leaks with valgrind with just ppcoind on testnet, with a single GPU.
If I pull out the valgrind logs / dumps for testnet on mining say 5 blocks, and again on 50 blocks, will it be of any use?
Dunno I feel there is quite a bit noise in the valgrind report. After generating ~100 blocks on my testnet node I got 3KB definitely lost, 6KB indirectly lost and 1KB possibly lost. And the stacks don't look plausible at causing GB range leak problems. It would most definitely help to have a reproducible setup where large amount of memory is known to have leaked. OK I'll leave it mining on testnet tomorrow for a good few hours. I have a good hashrate I can throw at it. |
|
|
|
There are still a few good people making their regular scheduled payments, but they remain the minority in BTCland
such as who?  x |
|
|
|
I tried valgrind on a testnet node with cgminer, but so far no luck finding useful clues.
Based on what I have heard so far, it seems this is related to getwork. Since a pool at most generate ~100 blocks a day, coinotron said he had to restart ppcoind once a day, I assume that ppcoind was eating >1gb a day, so this excludes the possibility the leak is related to valid blocks (each block taking about 10KB~100KB).
Now getwork does maintain a list of block candidates and a leak there could account for the rapid memory increase. I didn't change things related to allocation and delete of these block candidates and a code review there didn't reveal obvious problem either. I believe cs_main is also used to serialize getwork access so there shouldn't be concurrency issues with the block candidates.
Andy I seem to remember you were testing with some pool software earlier and also observed memory leak issue. Is there a simple way for me to set up a pool software and reproduce this situation? Can you all (Chris, coinotron, Andy) confirm my observations? How fast is ppcoind leaking memory in your production system? Is the leak speed roughly proportional to the number of getwork requests?
Thanks,
Didnt check if it was proportional to generate or getwork, as, hard to tell which - could even be to "mature", but I observed it as per below, prior to "mature" being reached. I was running a private pool for a while yes, I could set it up again, but the pool software wasnt the problem - I replicated the leaks with valgrind with just ppcoind on testnet, with a single GPU. If I pull out the valgrind logs / dumps for testnet on mining say 5 blocks, and again on 50 blocks, will it be of any use? |
|
|
|
What's this to do with ppcoin? I see "coiledcoin"? |
|
|
|
|
Show Posts
