6 Guidelines

6.1 Known Limitations

The main limitation in the use of the MOSEK Optimization Server are reported in this section.


Currently the MOSEK OptServer has been only tested on Linux 64bit machines.


Job submission using MOSEK API is only available starting from MOSEK 8.

Submitting jobs directly using HTTP commands is possible as long as the file format is accepted. However, it must be noticed that the compatibility does not depend on the OptServer but on the underlying MOSEK solver available on server machine.

6.2 Resources and performance

OptServer is a very lightweight server and requires very limited resources both in terms of memory and CPU.


The use of CPU/memory resources by OptServer should be neglegible.


Most of the network load is due to the transfer of the optimization problem from the client to the server. That happens in a single burnst. Therefore

  • For long running jobs the transfer time is typically neglegible,
  • For easy to solve problems the transfer time may be more significant.


The same problem can result in file of different sizes depending on the choosen format.

However, OptServer has not been designed for time critical production environment.

Disk usage

Each job is stored on disk along with log and solutions. The reasons are:

  1. avoid to keep jobs in memory while the solver is running,
  2. in case of crash, information can be recovered from the disk,
  3. solution and result can be recovered asynchronously reading from disk.

Therefore a suitable amount of free space must be available.

The folder used to store jobs information is under the basedir folder, that can be set in the configuration file.


OptServer does not delete data for completed jobs. Users of cloud services should take some care in case they pay storage fees.