{
"height": "12203",
"generationSignature": "b1a37ce33dabb5a1e1b5ebb2c4a4541f8bedeff75db1cf9d5f12145e51f424ae",
"baseTarget": "6892921",
"targetDeadline": "75000"
}
Found pool share: 545478820145454654:1509132
{
"height": "12204",
"generationSignature": "fdcc53de7a99a5f6ec65935981af77e300dd4a0ea91cfa04baf31d4eaf8ec862",
"baseTarget": "6329512",
"targetDeadline": "75000"
}
Found pool share: 545478820145454654:2596886
Submitting shares to pool
Received share/s
Hello, I've finally plotted my disk and after no luck with solo I'm connected to pool...
I'd like to ask how exactly does this work...
Sometimes my plot haven't been searched fully and new block comes first... Are those pool shares really submitted? Or does submit to pool process executes just after whole plot has been searched?
In the example above - are both shares submitted?
This seems to me that also size of plot & disk i/o are limiting factor. (Sometimes blocks comes sooner than my miner evaluates whole plot). How long does it take your miner to evaluate yours?
I'm currently plotted to multiple 25GB files... Is it problem? Do you use one file per HDD partition (e.g. 1 TB file)? Is there much of improvement with disk IO?
I'm using ext2, noatime... according to vmstat there is max 2000 kB_read/s disk reading during mining (so very mild without any significant CPU load).
Thanks in advance and thanks creators for this promising project!
