Is there plans to get the wallet and miner converted to C? Java just eats up too much ram and causes crashes/reboots, even if all the ram isn't used.
Porting the wallet to C would be a lot of work, and it would a pain to maintain and ensure compatibility between them. A C thin client wouldn't be out of the question at some point, but its not a priority. I've found that most miner issues are actually windows prefetching eating up peoples' ram, not the miner, however dcct did make a C miner also. Strange, I have prefetch and superprefetch off to avoid excessive writes to my my two rigs with SSD's on the OS drives. Must be something else causing it. could it be because of SSD ? i am using HDD and i never encounter any problem u have. Or maybe its because of solo mine ? I never solo mine before. I am satisfied with my payout on pool for many days. Why not give pool mining a try ? u might be surprise. Especially uray pool did a server upgrade recently and everything is better than before i have a similar problem mining plots on a NAS drive. Tried it on two different PC and both would periodically crash due to out of memory issues. i don't get this problem with 3 other drives physically connected to one of my PC. the NAS drive is formatted as ext3 whist the others are NTFS so i'm leaning to the fact there is a difference in reading ext3 based drive data? Windows needs a driver to read/write with EXT3/2 and I think Linux can read/write to NTFS with no issues. Maybe the coding needs a re-haul and be optimized more. |
|
|
|
Is there plans to get the wallet and miner converted to C? Java just eats up too much ram and causes crashes/reboots, even if all the ram isn't used.
Porting the wallet to C would be a lot of work, and it would a pain to maintain and ensure compatibility between them. A C thin client wouldn't be out of the question at some point, but its not a priority. I've found that most miner issues are actually windows prefetching eating up peoples' ram, not the miner, however dcct did make a C miner also. Strange, I have prefetch and superprefetch off to avoid excessive writes to my my two rigs with SSD's on the OS drives. Must be something else causing it. could it be because of SSD ? i am using HDD and i never encounter any problem u have. Or maybe its because of solo mine ? I never solo mine before. I am satisfied with my payout on pool for many days. Why not give pool mining a try ? u might be surprise. Especially uray pool did a server upgrade recently and everything is better than before Nope, SSD wouldn't be the issue. I did pool mining before, but I get better results solo mining. The pool miner is nearly similarly coded like the solo miner, it has to be either a memory leak and/or just not optimized usage of system ram in the java coding. |
|
|
|
Is there plans to get the wallet and miner converted to C? Java just eats up too much ram and causes crashes/reboots, even if all the ram isn't used.
Porting the wallet to C would be a lot of work, and it would a pain to maintain and ensure compatibility between them. A C thin client wouldn't be out of the question at some point, but its not a priority. I've found that most miner issues are actually windows prefetching eating up peoples' ram, not the miner, however dcct did make a C miner also. Strange, I have prefetch and superprefetch off to avoid excessive writes to my my two rigs with SSD's on the OS drives. Must be something else causing it. |
|
|
|
Is there plans to get the wallet and miner converted to C? Java just eats up too much ram and causes crashes/reboots, even if all the ram isn't used.
I have no problems at all with the java client. Its the miner/plotter that causes problems. Your Linux plotter works fine and the gpu plotter works good too. Just mostly the issue with the miner, it's crashes and cause a reboot on my rigs. The wallet is just optional to be ported to C. |
|
|
|
Burst 1.1.2Updated UI now has encrypted messaging, and DGS. Block generation bug fixed. There is no need for exchanges to update. Pools and solo miners should update. Other users do not have to update if they don't care about the new ui. https://mega.co.nz/#!WpQ0jAyY!BS8V9p-t3KrDEL1KtjKeg9MU__7aTRYrwwkhqvOlfqAsha256: 40ee7ef48cec883564ba95df3d35cbf038c603c5c5228996bce732b6bda7547f Is there plans to get the wallet and miner converted to C? Java just eats up too much ram and causes crashes/reboots, even if all the ram isn't used. |
|
|
|
Total of 60 TB mined 33K BURST as per today. Sold at 0.0000022 Rate with return profit of 0.0726 BTC to my BTC-e account.
POC another day another great profit to earn.
Please stop with that, we don't need to know your profits/losses. Stop bragging, that's childish. Please be mature. |
|
|
|
Please don't promote another coin in this thread. That has nothing to contribute to Burst. comon this coin is dead!!!!!!!!
That's your opinion if it's dead, then why are people still mining it? 205 o shit!!!   I can't decide if I should dump now to reduce the loss or just f*ck it, hold, and be a sucker bagholder... Hope you sold some in the beginning to make something. I sold half and hold the other half I mined, might buy some this week if the prices stay low. I didn't sell any. Last few days I'm thinking of buying more but falling trend seems to continue so now my thoughts are switched to dump instead of buy. Since I'm indecisive about this atm I'm now just holding and watching, and mine what I can. Gonna be fun when the price hit levels like 40 for 1  Please leave FUD comments to yourself. |
|
|
|
The java miner or wallet made my Window 8.1 machine crash with 50% of 14.4TB complete. Someone really needs to make a C version of both, they hog up too much ram. I don't even know what was my exact nonce that it crash at and just had to estimate to make a new starting point to finish the other half. Guess, I just going to make smaller plots from now on and just symlink or merge them.
You can always start with a higher nonce, they don't need to be in order. I know, but it's just annoying. Now the first plot is going to have errors in being read more likely. Might have to invest in more ram, looks like 16GB is the minimum. I don't know if it would be a good idea to merge the plots if one of them is incomplete. The java miner will give you an error when reading, but thats no problem. It processes whats in the file. You cannot merge incomplete plots - at least not with my merge tool. But you can use merged and non-merged plots together in one directory. Probably going to do a symlink and use one instance of the miner. |
|
|
|
Please don't promote another coin in this thread. That has nothing to contribute to Burst. comon this coin is dead!!!!!!!!
That's your opinion if it's dead, then why are people still mining it? 205 o shit!!! I can't decide if I should dump now to reduce the loss or just f*ck it, hold, and be a sucker bagholder... Hope you sold some in the beginning to make something. I sold half and hold the other half I mined, might buy some this week if the prices stay low. |
|
|
|
The java miner or wallet made my Window 8.1 machine crash with 50% of 14.4TB complete. Someone really needs to make a C version of both, they hog up too much ram. I don't even know what was my exact nonce that it crash at and just had to estimate to make a new starting point to finish the other half. Guess, I just going to make smaller plots from now on and just symlink or merge them.
You can always start with a higher nonce, they don't need to be in order. I know, but it's just annoying. Now the first plot is going to have errors in being read more likely. Might have to invest in more ram, looks like 16GB is the minimum. I don't know if it would be a good idea to merge the plots if one of them is incomplete. |
|
|
|
|
The java miner or wallet made my Window 8.1 machine crash with 50% of 14.4TB complete. Someone really needs to make a C version of both, they hog up too much ram. I don't even know what was my exact nonce that it crash at and just had to estimate to make a new starting point to finish the other half. Guess, I just going to make smaller plots from now on and just symlink or merge them.
|
|
|
|
Did you get the block?
Yes, the block #11966 is mine, the payout at doge94's pool was about 2800 coins. I haven't pool mined since the first week v1 pool was out, been solo mining since thereafter. |
|
|
|
Nice deadline :-)  Did you get the block? Damn 4 is super low, lowest I ever got was 101....lol |
|
|
|
Did I just I found a block?  Block=9500 coins Are you on a pool? I just noticed the date was 2 days ago and I started solo mining today. I was mining on a pool before. Maybe the block is oprhaned and the coins you received is late from the pool. So, I bought some BURST on c-cex.com and sent it to my wallet. The transactions show up in the wallet, but not in any of the blocks that were found after the transfer. It's been over 2 hours and they're still unconfirmed. What's wrong? Is this normal?
Since there appears to be more version 0 transactions from the c-cex address, it looks like c-cex might still be on 1.0.3, which would mean they're now on a bad fork, and those transactions won't go through. That could be very possible C-Cex still on an older wallet. |
|
|
|
Did I just I found a block? Block=9500 coins Are you on a pool? |
|
|
|
What happens when my deadline reaches zero while solo mining?
Never had a deadline lower than 101 and received a block. I would assume you get the block 100%...lol Seriously, there might be an issue..... |
|
|
|
is dev v2 pool ok? have not got payout for 8 hours ,usually payout every 4 hours
Seems fine. Is you wallet up to date? Some peoples' wallets seem to be getting stuck. I had a similar issue, I just restarted the wallet and it synced up fine. Hey burstcoin, what's next after you get the "BurstId authentication system"? Road map update? Any progress on making v.2 pool better and easier to join? Anyone finishing up a GUI wallet/miner/plotter, maybe coded in C? What's the hold up with Bittrex? You did the wallet update with the new NXT API. |
|
|
|
Does the gpuplotgen2.1.0... work properly with 14.*** drivers, because the ver. 2.0.1 generates plots that give huge value deadlines too...
Someone made the test and reported to me that the 14.4 driver is not an issue anymore with the new kernel (2.1.x). Righteous... I'll give it a go with 14.7..... Seem like I'm getting the same issue that plagued 14.4 on 14.7. I'll let it run for a bit and report on it after an hour plotting. If results are negative, I'll go back to 13.9... Update: It's mining fine now and the deadlines are getting lower, but both 14.4 and 14.7 are slower than 13.9 driver at the moment. I'll let it run for a little longer because it's still slowly, I mean slowly, gaining speed. MSI Twin Frozr III HD7970 BE Stagger=3072 Threads=128 Hashes=8160 Clocks=1050/1375(Core/Mem)[Default] |
|
|
|
Does the gpuplotgen2.1.0... work properly with 14.*** drivers, because the ver. 2.0.1 generates plots that give huge value deadlines too...
Someone made the test and reported to me that the 14.4 driver is not an issue anymore with the new kernel (2.1.x). Righteous... I'll give it a go with 14.7..... Seem like I'm getting the same issue that plagued 14.4 on 14.7. I'll let it run for a bit and report on it after an hour plotting. If results are negative, I'll go back to 13.9... |
|
|
|
Does the gpuplotgen2.1.0... work properly with 14.*** drivers, because the ver. 2.0.1 generates plots that give huge value deadlines too...
Someone made the test and reported to me that the 14.4 driver is not an issue anymore with the new kernel (2.1.x). Righteous... I'll give it a go with 14.7..... |
|
|
|
|
Show Posts
