maria-discuss team mailing list archive
Mailing list archive
Re: Performace issue with insert
Reindl Harald <h.reindl@xxxxxxxxxxxxx>
Sat, 30 Jan 2016 21:23:54 +0100
the lounge interactive design
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
Am 30.01.2016 um 21:07 schrieb walter harms:
Aktualy I do now some profiling now we want to see the differences when switching 31-1.
We used myISAM since the biggest problem is speed and immoDB showed to be crash sensitive.
We store long time series data so the system is writing data all the time.
for "writing data all the time" MyISAM is for sure a completly wrong
decision because the performance strength of MyISAM was always on
MyISAM *always* does a *complete table lock* for writes and don't allow
concurrent writes without locking - that don't scale when you write all
day long and there are table locks all day long
what do you mean with "immoDB showed to be crash sensitive" (besides i
assume you mean InnoDB) - MyISAM is crash sensitive and needs repairs
everytime something crashs - InnoDB is crash safe (as for as something
can be crash safe)
Description: OpenPGP digital signature