Open topic with navigation
Media Server provides asynchronous actions. Each asynchronous action has a queue to store requests until threads become available to process them. These queues are usually stored in a datastore file or in a database hosted on a database server, but in some cases you can increase performance by storing these queues in memory.
Storing action queues in memory improves performance only when the server receives large numbers of actions that complete quickly. Before storing queues in memory, you should also consider the following:
If you stop Media Server cleanly, Media Server writes the action queues from memory to disk so that it can resume processing when it is next started.
To configure Media Server to store asynchronous action queues in memory, follow these steps.
To store action queues in memory
If you have set any of the following parameters, remove them:
Set the following configuration parameters.
||A Boolean value that specifies whether to keep the queues for asynchronous actions in memory. Set this parameter to
||(Optional) The time interval (in minutes) at which the action queues are written to disk. Writing the queues to disk can reduce the number of queued actions that would be lost if Media Server stops unexpectedly, but configuring a frequent backup will increase the load on the datastore and might reduce performance.|
[Actions] UseInMemoryDatastore=TRUE InMemoryDatastoreBackupIntervalMins=30
Save and close the configuration file.
When you start Media Server, it stores action queues in memory.