nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Preparation" prior to downloading assets

jitendra

Hi,

Prior to downloading an asset from MediaBin, a sizeable amount of time is spent in "preparing" the asset for download. These steps seem to be followed even if one has not chosen a predefined image traansformation task.

I am curious to know what these pre-download processing tasks are.

Thanks
Jitendra

Find more posts tagged with

Comments

Migrateduser

My guess is that the server is copying the file to a temporary directory, from which it will then be sent to the final location (or made available via a link).

You never access the files directly in the MBDataDirectory.

Folco Banfi

lyman

Greetings. Every download from MediaBin involves a task whether you know it or not. The default is the (None) task, which in its own right performs a merge of all the metadata fields stored in MediaBin with those in the asset to make sure that what you get reflects any edits. For architectural reasons some invocations of thr (None) task are slower than they ought to be (specifically in the case of Multimedia, MS Office and Vector EPS documents). This is being addressed in later versions.

Furthermore, in some configurations the MediaBin server and the web server are separated by a firewall necessitating a so-called "transfer job" between them.

In the meantime there are two approaches to making this process faster. First, if you know you do not care about the metadata merging, the (Get Original) task is significantly faster than other tasks. Secondly, be sure to enable the "Derivative Direct" feature to allow the server to cache frequently accessed images.

Hope this helps,

Lyman Hurd
MB Server Team

MediaBin Server Team
Interwoven, Inc.