Am 31.01.2016 22:01, schrieb Reindl Harald: > > > Am 31.01.2016 um 20:44 schrieb walter harms: >> "crash sensitive" translates into: We had 3-4 occassions where an full >> backup was >> needed, and all had all to do with immoDB tables broken beyond repair > > InnoDB is transaction safe and much more relieable in case of crashes > when your hardware ist not broken at all because it has checksums > > MyISAM needs often a manual repair after crashes and is not really > reliable in such cases - just because it starts don't say anything about > how relieable your data are > > *please* spell InnoDB correct it hurts! > >
I will try to stay with InnoDB spelling :) Here are the test results: Both boxes are the same concerning hard/soft-ware except mariadb/mysql of cause. methode used: time -f „%E %w“ insert.programm Box mariadb 10.1: Total: 89274 Distribution max: [cnt] - [s] 22633 00.05 23448 00.06 12000 00.07 There is a second smaller peak: 1019 00.47 1109 00.48 1014 00.49 There is a huge tailing until 2.6 (usually 1 entry) Box mysql 5.1 Total: 68638 Distribution max: [cnt] - [s] 22766 00.02 11785 00.03 tailing until 0.56 I did no further analysis. re, wh _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
