Receive email notifications by changing your settings.
Click on your picture in the top right corner, go to Preferences and select your notification preferences.
Thank you for contributing to our forum!
Please keep in mind:
1. To only comment on the topic where the discussion is about. Do you have a new question or topic? Please start a new discussion.
2. Be kind to other users!

Long-running calculations

Recently, we have made a change in how calculation's in the Tygron Platform are queued and executed. Specifically, some of our calculation clusters are now specifically time-limited, meaning calculations will time out after 30 minutes. Other clusters allow for extremely long calculations of many hours. The idea behind it is that calculations which take long will be executed on a specific group of clusters, while shorter calculations, for example for instant-gratification impact sessions, still have computational resources available. We have made these changes to ensure a fair balancing between our various users to make use of our high-performance computing platform.

To properly use these options, please consider the following:


  • If you have a calculation which does not take very long (30 minutes is the hard cut-off), use the "Update now", "Reset Indicators", or "Reset X queries" options. These options will allow the calculation to take place on the time-limited clusters, bypassing calculations with a longer duration if neccessary and possible.
  • If you you have a calculation which does take longer (30 minutes is the hard cut-off), use the "Scheduled Updated" or "Scheduled Update (long running)" options. These options will only allow your calculation to run on the clusters which are not time-limited, so they can run to completion and are not in the way of quicker calculations.


Although it is possible to use either option at any time, you have final say on whether a calculation should be considered short or long, and thus whether to use either option. It is strongly recommended to use the appropriate function for your calculation. Using the "Update now" function, for longer calculations, for example, may lead to your calculation timing out without usable results.


As an addendum, for all users whom employ the API to perform calculations automatically:


  • Using the EditorIndicatorEvent.RESET_INDICATORS is equal to using the "Update Now" functionality, regardless of parameters.
  • Using the EditorSettingEvent.SET_SCHEDULED_UPDATE will prime the session schedule a calculation for a long running calculation instead. The first parameters is the timestamp in milliseconds at which to enqueue the calculation. Setting it to any moment in the past (-1 will do nicely) will enqueue the calculation almost immediately.


Sign In or Register to comment.