bad plotsize shown

[cchance27]

[10:52:52] Processed J:\Burst\plots\1567212183075360343_1000000001_1903760_1903760 in 5.714814 secs = 21.3201409529689 MBps
[10:52:52] Read J:\Burst\plots 0.12184064GB in 5.71489 secs = 21.1727591281058 MBps

[10:52:47] Processed I:\Burst\plots\1567212183075360343_900000001_508032_508032 in 0.9606363 secs = 33.8463662053995 MBps
[10:53:25] Processed I:\Burst\plots\1567212183075360343_900508033_7110424_7110424 in 38.4084982 secs = 11.8480845991526 MBps
[10:53:25] Read I:\Burst\plots 0.487581184GB in 39.369258 secs = 12.3700578761225 MBps

[10:53:04] Processed H:\Burst\plots\1567212183075360343_800000001_7618456_7618456 in 18.1166769 secs = 26.9133896183797 MBps
[10:53:04] Read H:\Burst\plots 0.487581184GB in 18.1167948 secs = 26.881134625425 MBps

I drive is a 130gb and 1.8tb plot shown as 0.12gb?
H drive is a 1.9tb plot but shows as 0.487gb?
J drive is a 487gb plot shown as 0.487gb?

All plots were created with the AIO client so xplotter I believe and are optimized by default.

[guytp]

I believe no issue in calculations but perhaps how it's displayed.

Reported is total amount read - only 1/4096th of plot size is read each loop.

Assuming all the files are reported here

H: 7618456 nonces = 2TB
I: 508032 + 7110424 = 2TB
J: 1903760 = 500GB

Total size (TB) = nonces * 64 * 4096 = bytes / 1000000000000 for TB

Amount read should be 1/409th so

H: 488MB
I: 488MB
J: 122MB

Total read (MB) = nonce count * 64 / 1000000

In the lines above reported:

H: 488MB
I: 488MB
J: 122MB

So it's displaying correct value for amount it has read - I'm guessing this is misleading due to the fact you expect to see plot size, rather than data read from plot.

Would a fix help to be something like

Read H:\Burst\Plots - 0.49GB of 2TB read in 18 secs = 27MBps

@cchance27

[cchance27]

Ahhh that explains it, I think the reason it was confusing is that at first glance it looks like it's only reading a few gigabytes of data on the drive and the rest is being ignored. Anything that acknowledges the full plot size was able to be used would be good for the user, perhaps even on load when the plots are initialized when the miner starts saying the size of the plot would be helpful.

The example you showed is also a big improvement on readability.