Just noticed that this account appears to be abusing the coin in some way, might be something to look into. They dumped a ton of empty assets on a few of my accounts and it's a ton of visual clutter and spam if nothing else.
Posts made by captinkid
What is this account doing? Spamming empty assets on accounts?
RE: Looking for massive file system sector size support
No such thing as a cheap 1TB flash drive, at least not the small thumb drives we know and love. If you bought it on Fleabay or Amazon and it's less than $500 it's a likely scam and it's just an SD card with a 32GB "If you're lucky" or so of storage space on it, but they hack the firmware to report more. Try filling it up and see how much it holds before it gives errors.
There are a very few legitimate USB drives out there or in development that have that capacity, but they're certainly not cheap or small. Currently only one made by Kingston is on the market that I can see and it's $734 for 1TB and it looks like a small brick.
Also the legitimate USB 1TB drives are astoundingly fast and should be USB 3.0, if it's USB 1.0 or 2.0 I can almost guarantee it's a fake sight unseen.
If you have the chance post the model # and manufacturer, and do your homework testing it out!
I keep a baseline of $/TB and anything that's below them is suspicious. Current baselines are around here from what I can find.
Regular HD ~$15+TB
USB STICK ~$400+TB
RE: Plot File Sizes
I like around 1TB myself. 3800000 nonces usually fits in 1TB of formatted space on most drives, fill with that size until it can't hold any more, then top it off with enough to fill the rest of the space minus <10000 nonces or so.
I wouldn't recommend a jbod array, as if a drive fails it'll can break many plot files across several drives. Also replotting the whole array for one failed disk would be a major pain!
Just plot and read each drive as a separate device and you'll have an easier time of it I think.
Fully optimized would be one file filling each drive completely. But that's unrealistic in practice and has multiple points of failure that just waste time during setup.
Best of luck!
RE: Pool Payouts. How do they work?
The 1498Q is how many burst you'll get when it hits the payout requirement, it should go from Q (queued), to U (unconfirmed sent). The other side of the + is how much has been paid.
The shares reward (898) is how many you'd get because of your current deadline if the pool wins that block. The historic shares (514) is what you'd also get if your pool wins the block regardless of your deadline that block.
RE: CreepMiner very slow
I'd suggest turning down your max plot readers # to test. Each is a thread and unless you have the bandwidth and CPU to actually scan 14 devices at once AND verify with three threads you're going to be going nowhere fast.
I have a mix of SATA and USB drives on my machines and I get the best overall processing speed (read + verify) with a plot reader number of 2-3. If you go too high you'll get seemingly faster reads but verification will lag and add overall time. In your case I think it's WAY too high.
Also Increase your buffer size a little if you have the ram 1024MB for 60TB would be good, 128MB is choking your read times I think, as the CPU maxes to fill the tiny buffer, then goes to verify, and then has to wait to fill the buffer again. It's completely overloading your CPU as my first guess, in a terribly inefficient way.
Also as Tinycoins said, get the newest version (1.6.3), it has a scan bar that differentiates between read data and verified data that makes it easier to visualize and optimize the process.
RE: The new official website is LIVE!
A minor grammatical error or two in the "A new way to make money" section.
"This is done easily with something almost everybody already has in his possession"
Should probably read as "their" instead" of "his" to be properly gender neutral
"Barrier to entry are very low."
Should probably make "Barrier" plural eg "Barriers"
RE: Wallet (1.2.9) / Node gets stuck all the time (shown in networkstatus but it seems to be correct), Wallet 1.3.0: good ?
I'm running 1.2.9 as well, best solution I've found is to have a cron job kill and relaunch the wallet every hour, that way it usually clears any stuck moments on it's own. If it's running as a service you can just call the service to restart.
You are out of sync for the ~3-5 minutes it takes to resync, but it keeps it going.
Hopefully someone can make a wallet that knows when it's stuck and can do what it needs to do on its own. From what I've seen even the 1.3.0 wallets get stuck.
RE: Does Pool location affect DL confirmation rate?
Pools have a minimum deadline they'll accept, some accept more some less.
Find one that gives you a confirmed deadline every few rounds and you should be fine.
RE: am I mining?
Looks like it's running fine but your plot file is a little small, so finding acceptable deadlines may be infrequent.
Might try a pool that is tuned for smaller plot sizes, as higher deadlines would be accepted. That pool looks like it has a limit of 8 days, so you're not going to get many deadline hits at all.
Some of the smaller size optimized pools have deadline allowances of greater than one month, look for those to start!