I work for Tiger Technologies, the hosting company mentioned by zigz.
The response that “Mint is working as designed” is a little surprising.
I want to emphasize that Mint is writing about 2 GB of data a day to MySQL for this site, but almost none of that data actually changes on each write. It’s updating an almost identical multi-KB “mint__config” database row over 100,000 times a day.
Our profiling shows that this single activity outweighs the rest of the site’s script/database load combined. During busy times, the simultaneous database UPDATEs can block each other, leading to measurable increases in script loading time. Database writes are extremely resource intensive compared to just running PHP code or doing database reads.
While it’s not causing any actual problems (we can certainly “handle the load”), our customer has indicated that he’s concerned about maximizing site performance at the millisecond level, and this is by far the main performance bottleneck on a fairly complex site.
We’ve looked closely at what Mint is storing, and almost all of the row data is identical on each write. Are you saying that Mint is designed to rewrite several KB of almost entirely unchanging data to disk for every page view — including irrelevant data like the activation key — just to track a few bytes of changed data (such as total and unique visitors)?
If so, we think that makes Mint inappropriate for any site with more than a few tens of thousands of page views per day. When performance really matters, a system that performs gigabytes of unnecessary disk writes is not a good choice.
If one aggregate value changes — say, the number of unique visitors for this hour, or the number of visitors from France — then Mint should just update that data., not rewrite everything it knows about from scratch. It could use a smaller database row dedicated to each aggregate value, for example. This change would reduce the Mint resource usage dramatically.
— Robert L Mathews, Tiger Technologies