6.0.0-beta1
7/8/25

[#6633] Performance query MYSQL
Summary Performance query MYSQL
Queue Horde Framework Packages
Queue Version HEAD
Type Bug
State Resolved
Priority 1. Low
Owners
Requester marco.curradi (at) asf (dot) toscana (dot) it
Created 04/22/2008 (6286 days ago)
Due
Updated 04/22/2008 (6286 days ago)
Assigned
Resolved 04/22/2008 (6286 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
04/22/2008 01:36:57 PM Chuck Hagenbuch Version ⇒ HEAD
Queue ⇒ Horde Framework Packages
State ⇒ Resolved
 
04/22/2008 11:55:29 AM Michael Rubinsky State ⇒ Not A Bug
 
04/22/2008 11:55:02 AM Michael Rubinsky Comment #3 Reply to this comment
I created an index on the table horde_datatree_attributes on attribute_value.
My problem seems resolved (I hope).
This index has been in CVS code since 9/30/07...along with other added 
indexes. You should check the scripts/upgrades directory for any 
others you may have missed.



On a related note, if your feeling adventuresome, there is a new share 
driver that does away with the datatree completely. It's currently 
considered 'beta' status, but is available for testing in the latest 
Horde CVS HEAD. In the administration settings, choose 'SQL' as the 
driver for shares and be sure to run the upgrade scripts located in 
the various [appname]/scripts/upgrades directory.
04/22/2008 10:54:59 AM marco (dot) curradi (at) asf (dot) toscana (dot) it Comment #2 Reply to this comment
I created an index on the table horde_datatree_attributes on attribute_value.

My problem seems resolved (I hope).


04/22/2008 08:58:39 AM marco (dot) curradi (at) asf (dot) toscana (dot) it Comment #1
Priority ⇒ 1. Low
New Attachment: horde_mysql.pdf Download
Patch ⇒ No
Milestone ⇒
Summary ⇒ Performance query MYSQL
Type ⇒ Bug
State ⇒ Unconfirmed
Queue ⇒ Kronolith
Reply to this comment
Hi we have some problem with a query:



SELECT c.datatree_id, c.datatree_name FROM horde_datatree c LEFT JOIN 
horde_datatree_attributes a1 ON a1.datatree_id = c.datatree_id WHERE 
c.group_uid = 'horde.shares.kronolith' AND ( a1.attribute_name = 
'owner' AND a1.attribute_value = 'marco.curradi' ) GROUP BY 
c.datatree_id, c.datatree_name, c.datatree_order ORDER BY 
c.datatree_order, c.datatree_name, c.datatree_id;



This query use the CPU at the 100%.



We have this problem only the users connection are about 20-30 or more.

This query use the disk  and if running 3-4 this query the process of 
Mysql use the 100% of CPU.

This query find 1 record but move 15000 record on temp (see the attachment).

I think the problem is the ORDER BY. Is necessary to use ORDER BY ?



thanks for your help


Saved Queries