Am 27.01.2016 20:05, schrieb Tom Worster: > Hi wh, > > If a table has any indexes then inset time increases with the number of > records in the table. Even with only one index, the difference between > inserting when the table is nearly empty and when it has many millions of > records can be dramatic. > > If you have some understanding of how conventional indexes work then this > effect can become fairly easy to imagine. >
It is not that easy, since tables in my test 10.1.10 and mysql 5.1.53 have the same setup. I would not be surprised if the difference had been 10% or so. But the actual difference is much more, causing jobs to pile up at peak times. Unfortunately i have correct my self at one small point the engine is MyISAM. re, wh > Tom > > On 1/27/16, 5:27 AM, "Maria-discuss on behalf of walter harms" > <[email protected] on behalf of > [email protected]> wrote: > >> Hello list, >> i have a strange problem with inserts. >> The tables is large (time series data) and has a >> lot of partitions, engine is IMMODB. >> We have notice that the write performance decreases with >> time, start of the month good, end of the month bad. >> >> The same behavier is the lasted version of mariadb. >> But when i replace mariadb with mysql the problems vanishes >> (so its not a hardware issue). I suspect that it is a caching >> problem but a comparison of the configs did not give a hint. >> Anyone an idea what may cause the effect ? >> >> >> 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 > > _______________________________________________ Mailing list: https://launchpad.net/~maria-discuss Post to : [email protected] Unsubscribe : https://launchpad.net/~maria-discuss More help : https://help.launchpad.net/ListHelp
