Plesk Expand Optimizations

[DimiterN]

Hello all,
I'm trying to implement some database optimizations for mysqld (which is used by Expand) and I have noticed some facts:
- We (in our company) haves two Expand servers : on first all Expand's tables uses MyISAM storage engine (SE), but on second - a lot of tables uses InnoDB SE. Is this normal? Or is caused by some database optimizations by Expand itself?
- Both machines where Expand is installed haves a high load (1.70 - 2.10 for InnoDB's Expand and 1.10 - 1.20 for MyISAM's). Is this normal for mysqld to take 100% CPU load of one core/process all the time?
- It is normal that expandom causes high load time to time (I think this is derived by 30 seconds update checks of expandom) and could be this period adjusted?
- It is possible some SQL queries to be optimized. E.g. queries like this:

SELECT DISTINCT
csoi.dns_server_id,
cso.id

FROM
cdns_zone AS cso

LEFT JOIN
cdns_zone_instance AS csoi ON cso.id = csoi.cdns_zone_id

INNER JOIN
plesk_dns_zone ON cso.dns_zone_id = plesk_dns_zone.id OR csoi.dns_zone_id = plesk_dns_zone.id

LEFT JOIN
dns_server_repository ON
(csoi.cdns_zone_id IS NULL OR csoi.dns_server_id = dns_server_repository.id) AND
plesk_dns_zone.server_id = dns_server_repository.server_id

WHERE
dns_server_repository.server_id IS NULL AND
(csoi.cdns_zone_id IS NULL OR csoi.dns_server_id IN(12))

ORDER BY
csoi.dns_server_id, cso.id

Is there some optimization tutorial/manual or something like this?
Where I can find more detailed information about Expand's database structure like EER diagrams and so on?

Every help in Expand optimization will be very appreciated.

Sincerely yours: Nikov, Dimiter

P.S. Excuse me for my bad English

[DimiterN]

Seems that nobody in Paralles Team is not concerned about optimizing their crappy software.
Shame on you guys...