We are planning to store video files (mp4 files) as part of domino documents. The files will be anything up to 800MB-1GB. The documents will be accessed via web (https). We are able to play the video when it is a part of the document but we are not able to move forward or backwards. Basically the video plays sequentially, you can only stop it or refresh the page.
When we moved the video to file resources and accessed that, the video takes a long time to start but we can move forward or backward. But the movement is not instantaneous, it takes long time as the server searches for the right start.
When we moved the video into the domino/html folder, it started immediately and we could move forward and backward instantaneously.
We do not have DAOS enabled on our server therefore I could not test. Do you know if the database was DAOS enabled could we get the same behaviour as when the video was stored in domino/html?
Additional info: Apparently the issue is the attachments are being compressed by Huffman compression an therefore not available for byte range serving. When they are not compressed they can be byte range served and the access is much faster but is still much slower that when served from domino/html folder. Info on how to prevent an attachment from being compressed is here: Disabling LZ1-compression for uploaded files via XPage xp:fileUpload (byte-range serving related)
My question reduces to: Would moving attachments to DAOS enable the Domino http server to serve the attachments faster?
I converted the database so that it is DAOS enabled. I did not do any formal measurements but just by look and feel I did not see any visible improvement in the speed of serving the file. It was the same as when the database was not DAOS enabled. Also ByteRange serving did not work
When leting Domino serve the file as a file from the file system direct, the increase of speed was noticable and ByteRange serving worked as expected and desired.