I have eBoostr installed on a Win 7 64-bit OS, 6GB RAM. I have an older 4-drive RAID SSD Array. When I run ATTO on it, starting at 16KB I get read speeds of 92MB/sec on up to as high 494MB/sec at 8192K transfer size, yet eBoostr reports only 56MB/sec transfer rate, which is just plain wrong. Even a single SSD drive from that array could kick out a sustained read of over 100MB/sec.
What is going on? Is eBoostr using a very small block size in it's testing? I also have an Acard RAM drive that is being reported at 115MB/sec., yet I can easily get 220+ MB/sec sustained reads when transferring digital video files between in and a Gigabyte iRam Drive, so I know it's way faster than eBoostr is reporting. It's also saying the iRam drive is about 50-70MB/sec slower than I can read from it with other files.
It seems this latest iteration of eBoostr is failing to take advantage of what my RAM drive and SSD RAID 0 array can offer, at least relative to ATTO and my anecdotal testing of read speeds. Even if Eboostr is using tiny files, a RAM drive should not care less, even if an SSD array did due to flash block size, etc.
Any thoughts?
How exactly does eBoost compute read/transfer speeds when it reports them? It's certainly not taking advantage of what my drives can offer.