Administrace komentářů

jak jsem jiz rikal - doporucil mi to jeden clovek, ktery se vyzna v tom, v cem ja zacinam.

toto je kratky popis: Hi, I just found that on servers with high user load (from 50-400) is better with InnoDB database structure. Why? Because MyISAM takes high cpu load when making queries, so InnoDB give you much more faster responses. I just made some mysqld tunning, and now my database take only half of CPU load then before with MyISAM. Just think about it. MyISAM needs proper optimisation, and after a day, DB is really slow. But with InnoDB, there can be optimization only once a week. I have tryed som queries with MyISAM and InnoDB. What took MyISAM almost 10 seconds, took InnoDB only 0,3 second, so its really much more faster. I made some script which transform already existing MyISAM tables to InnoDB. Only problem was with character table, which uses index key which can´t be altered. So best solution is export character table, manually edit it, remowe that index key and leave only key syntax, and import it back (you can edit engine manually in that export, so no more altering will be needed).

I have played a bit with mysql tunning. I have found variables, which makes my database really stable, fast, and not eating my memory or CPU too much.

Bohuzel anglictina neni moje parketa ten clovek ktery mi to navrhnul bohuzel neni k sehnani...

je mozne, ze ta struktura co mam ted dela tyto chyby, ktere shazuji ten hlavni program, ktery zapisuje/cte z databaze - nebo to je chyba toho programu, nebo ma chyba? - /var/log/messages

Jan 30 09:41:37 Nes kernel: mangosd[6535]: segfault at 00000000000000ba rip 00000000005bd276 rsp 00000000437fd9f0 error 4 Jan 30 10:29:02 Nes kernel: mangosd[18852]: segfault at 00000000000000b9 rip 00000000005bd496 rsp 00000000437fd9f Jan 30 11:01:42 Nes kernel: mangosd[20660]: segfault at 0000000000000204 rip 00000000005c4654 rsp 00000000437fda0 Jan 30 13:22:45 Nes kernel: mangosd[20887]: segfault at 0000000044e38008 rip 000000000057baa0 rsp 0000000043805d38 error 4