Hierarchies may take a long time in order to be fully built in memory at the server and they can be quite expensive in server resource terms (CPU, memory,…). Therefore some server optimizations are supported by Links Hierarchy:
- Server breath interval: every 250 ms, the thread building the hierarchy sleeps for 100 ms. This will take more time to get the data, however, it will avoid long peaks of high CPU usage.
- Server time out threshold: a time out of thirty seconds has been introduced in the server. The server tracks the time spent building hierarchies, if the timeout is achieved then the building process will be interrupted and the current partial hierarchy sent back to the user's browser and the issues no fully loaded due the time out will be highlighted with a red rectangle: