| 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 (6309 days ago) |
| Due | |
| Updated | 04/22/2008 (6309 days ago) |
| Assigned | |
| Resolved | 04/22/2008 (6309 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Queue ⇒ Horde Framework Packages
State ⇒ Resolved
My problem seems resolved (I hope).
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.
My problem seems resolved (I hope).
Priority ⇒ 1. Low
New Attachment: horde_mysql.pdf
Patch ⇒ No
Milestone ⇒
Summary ⇒ Performance query MYSQL
Type ⇒ Bug
State ⇒ Unconfirmed
Queue ⇒ Kronolith
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