I was involved in a version 3 project a few months ago and had problems with slow queries caused by a lot of nodes. I added some indexes the and it made dramatic changes to the performace of the admin GUI. So my question is, had anyone run a profiler/analyzer on the database? I think there's a lot of performance to gain here. Another thing I noticed is that it for example in the cmsDocument table uses a GUID as a primary key which isn't recommended.
GUIDs as primary key has its advantages and also disadvantages. It is the same with autoIds they have some pros and cons. So IMHO it can be ok and in some points not. The perfomance isn't so bad for Guids as PKs on SQLServer 2005 on mySql I don't know. But for developer Guids can be much easier.
Also I agree, the database isn't very well optimized, but as I know the database will be reworked for v5.
Umbraco Database
Hi
I was involved in a version 3 project a few months ago and had problems with slow queries caused by a lot of nodes. I added some indexes the and it made dramatic changes to the performace of the admin GUI. So my question is, had anyone run a profiler/analyzer on the database? I think there's a lot of performance to gain here. Another thing I noticed is that it for example in the cmsDocument table uses a GUID as a primary key which isn't recommended.
Any thoughts?
GUIDs as primary key has its advantages and also disadvantages. It is the same with autoIds they have some pros and cons. So IMHO it can be ok and in some points not. The perfomance isn't so bad for Guids as PKs on SQLServer 2005 on mySql I don't know. But for developer Guids can be much easier.
Also I agree, the database isn't very well optimized, but as I know the database will be reworked for v5.
Also you can see the blogpost from hendy for some improvements: http://blog.hendyracher.co.uk/umbraco-database-part-1/
Cheers, Thomas
is working on a reply...