DXA_Live\BinaryData disk usage - we have to inform our hosting partner

Question

Till now we had published the (non DXA) website files on disk.

With the DXA application content will come from broker database and we can expect a lot of write/reads to folders for example BinaryData\tcm-96\media. We have to inform our hosting partner for how many time this will be used (compared with non DXA).

My questions are:

• Where is BinaryData..\ used for (images, pages, content) ?
• What load can we expect on folder BinaryData... ?
• Is it more then once? How is this handles in the DXA Framework ?
• Will there be more then .. % load then in the before DXA ?
• Who is deleting old (cashed) files from BinaryData.. ?

Thanks in advanced for anwering.

Answer 1

• Where is BinaryData..\ used for (images, pages, content) ?
  • The BinaryData folder structure is a FileSystem cache for so-called Static Content Items. That is: binaries, assets and configuration files (stored as Binary in the database). This file system cache results in much better performance and less load on the CD database.
• What load can we expect on folder BinaryData... ?
  • Each incoming request binary data will result in a file read. File writes are much less frequent (only when a new binary is published or an existing one is updated).
  • DXA includes HTTP cache headers for the Static Content Items which make the browser cache them client-side and not request the same item multiple times.
• Is it more then once? How is this handles in the DXA Framework ?
  • I don’t understand this question
• Will there be more then .. % load then in the before DXA ?
  • Load on the BinaryData cache will be similar to load on the File System when binaries are published to File System directly.
• Who is deleting old (cashed) files from BinaryData.. ?
  • It is best to schedule a job which removes old files on a regular basis.