Closed deinhofer closed 5 years ago
not related any more, as HW is getting faster anyway. Nevertheless, the submit timeout of ARE tasks should be reduced a bit, otherwise it hangs too long in some cases.
If the timeout is too low or too high, it can be configured, see https://www.asterics.eu/develop/ARE.html#change-model-task-submit-timeout
The configured default timeout values when executing a task with the ARE model executor thread are good for a standard PC. If the ARE runs on a RPi the timeouts might be too short especially if scanning of serial ports is activated.
So for such a case, it could be useful to multiply the configured timeout value by a heuristic e.g. determined when calculating MD5 sums of plugins?