read calls are slow for SeekableInputStream impl backed by remote storage.

[brahul]

Calls to read() are slow (network letancy), when the implementation of SeekableInputStream is backed by a remote storage.
IMHO ,Ideally we should be making more of block calls (read(buf,off,len)) whenever possible.

Method void storeMetadata() : reconstructs the offset map from header information in the stream.
It is reading already available bytes using read() calls , which is extremely slow for our case (remote storage). These bytes are already available while reading the initial readSize (= 32 * 1024) length of data.
We can resort to read() , if the already available bytes doesn't have the trailing 0 byte marker.

Please advise.

[brahul]

@r4ruchir Did you get a chance to look into my request ?
If you want , I can provide a PR for the fix. We are using Gzinga against a remote streaming source for data and this fix is real helpful.

[r4ruchir]

Hey, Sorry, did not get chance to look at it. Can you provide PR if possible?

…

Sent from my iPhone On 30-Mar-2017, at 3:31 PM, Rahul Bhattacharjee <notifications@github.com<mailto:notifications@github.com>> wrote: @r4ruchir<https://github.com/r4ruchir> Did you get a chance to look into my request ? If you want , I can provide a PR for the fix. We are using Gzinga against a remote streaming source for data and this fix is real helpful. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#5 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AOPM_gI9rRAIYEVKZyAvnZq7rQJsvJpaks5rrC0EgaJpZM4MmAP6>.

[brahul]

Sure. submitted a PR. thanks,Rahul