I've been busy lately, and somehow missed the notification mail telling me you replied.
Thanks you for your reply.
a) Let's say around 200 pages. A few dozens of page templates, though.
b) Possibly, since there are several servers. But the slowness issues are definitely not due to the application starting up or cache issues, in case that's what you had in mind. Because it can happen as you simply refresh the page after having loaded it.
f) I can only do that on the test environment (otherwise, I have to contact another team). Right now, it fluctuates between 260 and 300 MB. The max we've seen was around 500-600 MB.
We also have a separate app pool for each of our Sitefinity sites.
Also, I turned the data caching off, but there's still another cache for the HTML code in Sitefinity, from what I understand.
"Just out of curiosity - are you expecting more traffic or why is it spread across servers."
Yes, we expect more traffic. Also, it's a mutualized farm.
"Maybe one Server with chaching would improve stuff."
Data caching must be disabled in a multi-server environment, though, according to the Sitefinity team. It's actually disabled automatically if you enable load balancing.
By the way, we found out we had a certain page that caused issues. It
just crashed the app when viewed from the front. From the back, we had a
"Cyclic child/parent relationship. A control/layout cannot be the parent of its own parent."
exception. After remaking that page, this helped the stability.
We still have stability issues, though. Looking at the Error log, we have exceptions such as "BackendError
: Telerik.OpenAccess.RT.sql.SQLException: Timeout expired. The timeout
period elapsed prior to completion of the operation or the server is
One of our contributors also had this error while using the back office. I brought this up here
Thanks for the link, I'll check it out.