Recommendations of CalculationMode in xTour2

[Bernd Welter]

As you know we offer the PlanToursOptions

• com.ptvgroup.xserver.xtour.CalculationMode : [PERFORMANCE | STANDARD | QUALITY | ...
• com.ptvgroup.xserver.xtour.PlanToursOptions.enableOptimizationPremium [true | false]

As I get asked for a recommended combination of these values I want to give some generic advice with a focus on PERFORMANCE | STANDARD | QUALITY:

If PREMIUM is set to TRUE

• We recommend QUALITY (as it makes no sense to combine Premium with STANDARD or PERFORMANCE)
• If you want to enable Premium in an on premise environment we recommend to increase the server configuration value : xtour.maxNumberOfThreads (e.g. 4 instead of 1) : Maximum number of threads to be used by the xtour service. The default is a single thread service. Increasing the number of maximum threads can lead to performance improvements because the xtour service can execute certain tasks in parallel. Notice that this parameter is just an upper bound on the number of threads, it is not assured that the xtour service uses this maximum number (e.g. if there are not that many threads available on your machine).

If PREMIUM is set to FALSE ...

• QUALITY : recommended
• STANDARD : only if you are looking for a quick solution where QUALITY takes too long
• PERFORMANCE : gna.. doesn't make sense at all on production - only for generic tests of the interfaces

Timeout

• Just in case you are thinking to use a module timeout: not recommended

Practically a proper setting should be based on some experiments regarding typical usage scenarios.