dreport I/O max 50MB/sec

[Fairlight]

If raw reads elsewhere are 1600MB/s, and filePro reads in sort/select are
50MBs, what does that tell you?

It tells -me- that it's likely a CPU bottleneck on a single-threaded
process on a single core, actually processing what it's reading, rather
than -just- reading from disk.  Sort operations are not free, you know.

Do this:

Create a large file, say 20GB or so (assuming a 64-bit OS).  Write
processing which simply does OPEN/READ in a loop/CLOSE and gives you a
calculation of how long it took.

Betting that test is far faster than sort/select.

m->

On Wed, Aug 07, 2019 at 08:38:30PM +0000, hutpjs+2i1bdow--- via
Filepro-list thus spoke:
> Sort select or any long or any read has a maximum 50MB/s which draws out
> a long time when working with larger key. Non fP application real world
> reads using full available IO (~1600MB/s) Tested on a various windows
> machines running fP locally.
>
> Does anyone else experience such limited throughput? Any suggestion to
> improve IO of dreport read?

-- 
Audio panton, cogito singularis.