Hi.
There are no defined hard coded limit about the number of paths in an interlocking tower or about the number of path objects inside a path. But there are a few operations where a tower needs to scan alll its paths and for each path all its path objects, so for performance a tower is sensitive to the total number of path objects defined in its paths. Normally these few operations are always done under specific threads inside the tower using some specific methods to avoid script timeouts, but the processing time remains dépendant on the total number of path objects inside a tower, which should remain reasonable. My advice is to avoid having more than 600 paths objects definitions per tower and performance is better with more paths with a low number of path objects than having a few paths with quite a lot of path objects.
Keep also in mind that using dynamic path object ownership helps to split paths between towers : the only remaining constraint being that all paths starting at the same entry signal needs to be in the same tower. Take care also that overlapping paths are not authorized : a path cannot be extended beyond another path entry signal on its way …
Hope this helps. If you need more advices or help, just ask, and thanks for your interest in using EITs.
Regards.
Pierre.
