|
After upgrading to ETK 1.4.4 from 1.4.2 we are getting complaints that the website tree takes a long time to open.
We have spend time finding out why, after looking with a profiler it seems the code spends a lot of time in the
ETKSiteManager's findBestMatchingSites method. We do have a lot of site definitions (40+) and it looks like the code
loops over them quite a lot. Interestingly the JCR tree in the Tools section doesn't suffer from this problem.
Also directly calling pages in a site (on author) does not cause significant slowdown, probably because
the code matches early.
|