Unsolved
This post is more than 5 years old
2 Posts
0
475
March 28th, 2013 05:00
Optimal Byte Range when downloading in chunks from Atmos
Hi,
I have a small test program which is using the Atmos version 2.1.0 of the Atmos java connector: http://code.google.com/p/atmos-java/
I am making use of the Object space API when uploading/downloading files from Atmos storage.
I am uploading a 15M file to atmos 10 times.
After all the uploads are successful I then read each file in turn using the AtmosApiClient.readObjectStream(objectId, ...) API. The chunk size is set at 1M.
I am able to successfully stream bytes from Atmos for 2 files. Reading of the 3rd file "hangs" after reading up to 5M.
I am wondering if I should be using a different chunk size to make more efficient use of the rest API ?
Is there a reason the test hangs ? I so not see any Atmos runtime exception.
When I reduce the size of the file to 10M then I can successfully download/stream all files !
Thanks for you time and help,
J.



JasonCwik
281 Posts
0
March 29th, 2013 11:00
When reading from a stream, chunk sizes of 1MB should be good. Please double-check you're closing all stream handles; it's possible you're running out of connections in the connection pool used by the API.
Can you reproduce this against api.atmosonline.com? Can you share a sample program?