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; } } }

MediaBin Jobs appear to be running sequentially?

nate25

I added a large file (60MB video file) to MediaBin, and then two smaller files (1MB each), and I noticed that the smaller files' job didn't complete until the job for the large file did. It took almost 3 minutes for the large file job to complete, thereafter the small files' job completed in a matter of seconds.
Since MediaBin runs multiple jobs concurrently, shouldn't the smaller files get uploaded before the larger file? I tried lowering the priority of the large file's job, but that didn't help.

I checked in Enterprise Manager and the Max Concurrent Jobs is set to 5.

This presents a problem as our users are planning to add videos to MediaBin soon.

Here are the Job History entries (First time is the start time, the second is the finish time):

Completed Normal Insertion Picture-002.jpg Picture-002.jpg (Insert Unmodified) 10/27/2008 1:42:59 PM 10/27/2008 1:45:57 PM CORPORATE\TestUser
Completed Normal Insertion Picture-001.jpg Picture-001.jpg (Insert Unmodified) 10/27/2008 1:42:49 PM 10/27/2008 1:45:55 PM CORPORATE\TestUser
Completed Low Insertion hemmy awards export 102108.mp4 hemmy awards export 102108.mp4 (Insert Unmodified) 10/27/2008 1:42:25 PM 10/27/2008 1:45:53 PM CORPORATE\TestUser

Find more posts tagged with

Comments

lyman

The video support in MediaBin is actually handled by the DirectX library provided by Microsoft. This is a customizable set of DLL's and customers can register new codecs outside the context of MediaBin. Unfortunately we have found that not all DirectX codecs are safe to run simultaneously and we have made the conservative choice of safety over performance by making these jobs run sequentially. Other image formats will be launched at the same time as a video processing job.

We understand that this is a sub-optimal solution and we are actively looknig into ways to avoid having to do this.

Cheers,

Lyman Hurd

nate25

Lyman

Thanks for the response.

I ended up filing a support case for it, and the support person (May) said that the file transfer/upload process (or whatever it's called) runs sequentially. We ended up filing a feature request for it. FYI We also noticed that the actual file uploading is much slower if done via MediaBin that via Widnows explorer - i.e. uploading a 60MB file directly from my machine into MediaBin took three minutes, but if I copied the file to the MediaBin server, and uploaded it from there into MediaBin, the whole process took only around one minute.

Regarding your explanation, since I uploaded via "Insert Unmodified" task, I would think it's not doing any conversion, but maybe that's an incorrect assumption.

lyman

Some more background.

The majority of MediaBin primitives are not serialized. Unfortunately multimedia is an exception for the reasons cited above.

The (Insert Unmodified) task is responsible for creating thumbnails and extracting metadata, and so there is non-trivial work especially for video for which we also produce a streamable preview.

Inserting from the web client involves an extra hop from the browser to the web server and then to the MediaBin server. If feasible, the fastest way to insert large files is to upload via the Windows Native Client and in that case it is significantly faster if you refer to the files via a UNC path visible to the server instead of a local drive. This is because when the client sees "C:" it cannot tell whether that address is server-local or client-local (I know in this case it would be both but the software doe snot know that!) and it transfers the file to a staging area prior to ingest.

Cheers,

Lyman Hurd