Table of Contents
Preface
Performance Profiles can be used to optimise just:store’s data throughput for certain applications like ingest, playout or video editing.
Changing the Performance Profile
Before continuing make sure to read the article Connecting to the just:store Web-based Administration Interface
Click on Profiles in the sidebar.
Click on the Activate button of the profile which suits your needs best.
Changing a profile is done in real-time by just:store. Processes which are already running will not change their priority
Available Profiles
Playout
The system is fully optimised for real-time read operations. Write operations will be slower, but do not affect read operations.
PROs | CONs |
---|---|
prioritize read operations | write operations will be slower and less important. |
better performance for reading operations shorter response time for each package |
Editing
The system is optimised for a high amount of read/write requests. The I/O performance is shared between read and write operations.
PROs | CONs |
---|---|
Write and read operations will have the same priority. | If the usage is mainly for playout the write operations will have the same priority and can increase the response time for reading operations. If the usage is mainly for ingest the read operations will have the same priority and can increase the response time for writing operations. |
Not slowing down any operations (except using bandwidth limitation). | |
Best profile for bandwidth limitation. | |
Principle of handling all requests will be FIFO*. |
Optimised Setting for Ingest
The system is fully optimised for real-time write operations. Read operations are slowed down in favor of writing.
PROs | CONs |
---|---|
prioritize write operations | read operations will be slower and less important |
better performance for writing operations shorter response time for each package |
*FIFO
is a method for organizing the handling of a queue of requests where the oldest (first) entry, or 'head' of the queue, is processed first.