Job Queue
The Job Queue allows you to easily setup and run a Server on a powerful machine onto which multiple users can submit their demanding simulations. Submitted simulations or Jobs are then queued, started automatically and executed sequentially without the need for complex scripts or manual intervention. The sequential execution ensures that the simulations do not compete for CPU cores, available RAM and GeoDict licenses. You can also run a local job queue server on your machine for executing multiple queued jobs overnight or over the weekend.
To start a job queue server, a GeoDict-Server license is required. The job queue server starts each submitted job in a separate GeoDict instance similar to the execution of a macro in the command line. For this, it requires a GeoDict-Base license and licenses for the currently used modules and processes. Users that want to submit jobs require another GeoDict license for their local machine.
The Job Queue was first introduced in GeoDict 2024. In GeoDict 2025 several improvements were made to make this feature more intuitive and user-friendly:
Important! For the Job Queue to work, the Client and Server machines need to use GeoDict with the same major (e.g., GeoDict 2025) and minor (e.g., Service Pack 1) version. If the version between Client and Server is different, a corresponding log message is printed. |
Topics of this section |
|---|
|
Join the conversationVisit the Community on GeoDict Forum to be inspired and get answers to top questions. |