Umbraco runs too slowly when using remote database
Hi, this isn't a simple bug to fix but I think it could do with some attention as there are a few people complaining about it: Umbraco (the backend) runs very slowly when connecting to a remote database.
Running Sql Profile quickly reveals the issue: far too many database calls are being made.
For example, publishing my homepage, which is fairly simple, causes about 269 database calls! Many of these calls are running the exact same SELECT statements. As a result, it takes about 20-30 seconds to publish one page.
Perhaps some of these statements should be cached to avoid database calls. For example, the statement select sortOrder from cmsTab where id = ## is executed about 60 times, taking about 2 seconds in total. It should be very easy to reduced this to 1 to 4 call taking only a few milliseconds!
Another offender is SELECT ### FROM cmsPropertyData WHERE id = ## - there are about 110 such calls. Again, with a little bit of caching or rearrangement, this could be reduced to less than a half dozen database calls.
Umbraco runs too slowly when using remote database
Hi, this isn't a simple bug to fix but I think it could do with some attention as there are a few people complaining about it: Umbraco (the backend) runs very slowly when connecting to a remote database.
Running Sql Profile quickly reveals the issue: far too many database calls are being made.
For example, publishing my homepage, which is fairly simple, causes about 269 database calls! Many of these calls are running the exact same SELECT statements. As a result, it takes about 20-30 seconds to publish one page.
Perhaps some of these statements should be cached to avoid database calls. For example, the statement select sortOrder from cmsTab where id = ## is executed about 60 times, taking about 2 seconds in total. It should be very easy to reduced this to 1 to 4 call taking only a few milliseconds!
Another offender is SELECT ### FROM cmsPropertyData WHERE id = ## - there are about 110 such calls. Again, with a little bit of caching or rearrangement, this could be reduced to less than a half dozen database calls.
is working on a reply...