It's a list of known problems with MySQL, most of which violate the "Principle of Least Surprise".
Some of the problems have performance implications. The query planner stuff, for example.
> The funny thing is that this blog's performance is based on some cookie. If I reload in Chrome? 2 sec ... just stop ... when you don't even know what you're talking about.
It may interest you to learn that web browsers have local caches. Incognito Mode does not have such a cache, and so must refetch pages from scratch on each view.
I'm genuinely interested to learn which use cases are more dependent on query planning than caching methodologies.
I'll reply to this separately, it's a good discussion to have.
My basic problem is that caching comes with a coordination cost and I prefer the originating data source to be as performant as possible.
My own use case is a small Wordpress multisite installation. Even with a relatively trivial amount of traffic and site data, it behaves abysmally on some simple requests. The linked article seems to explain why -- the query planner ignores indexes on certain kinds of joins. The same sort of joins as the Wordpress Recent Comments Widget.
Now, I can and have worked around this by using multiple layers of caching. There's the MySQL query cache, some memcache (PHP opcode caches would in theory be quicker but I've never been satisfied with their stability) and of course pumping gzipped HTML to disk for nginx to serve directly without hitting PHP or MySQL.
But like I said, caching comes with a coordination cost. One of my sites is used less like a blog and more like a chat room. Hundreds of comments per hour, every single one of which causes the query cache to be pruned of the exact query I most need to cache in the first place.
That is: I need to cache this query because they talk so much. But they talk so much that the cache is not that helpful.
What would be helpful is if MySQL was a bit smarter about using the indexes I put there in an apparently useless bit of chicken-waving.
mysql proxy might help you out, or mysql triggers, or plenty of easy indexing strategies.
i agree, caching strategies are not easy, but that is not the fault of databases. IMHO keeping your data layers separate is best.
if you have a multi-site installation, set some kind of prefix within the app that makes sense to you for each application, before it goes into whatever cache.
this will work for you whether it is shared memory, memcached, or some kinda file situation.
But that was his whole point - needlessly complicating an otherwise simple setup to get around limitations in the DB engine.
> mysql proxy might help you out, or mysql triggers, or plenty of easy indexing strategies.
I genuinely fail to see how mysql-proxy [1] (which has a sleuth of long-standing, unfixed, problems on its own), or triggers would (elegantly) help in this situation.
[1] http://dev.mysql.com/doc/refman/5.1/en/mysql-proxy.html
edit: formatting
And what? It's the reason to not use caching? ridiculous
If you poke around, you'll find that this isn't a Wordpress installation. (Or any other dynamic blog engine, for that matter.)
It's Markdoc[1], a static site generator:
> Markdoc converts wikis into raw HTML files and media ... Markdoc need not be installed on the hosting site, since the resultant HTML is completely independent.
I believe the program at fault here is Apache, which in the default configuration loves nothing better than to choke on child processes.
Instead, this author his simply focused on numerous detailed aspects of MySQL that he/she seems to think would be seen by most people as particularly insane, without need for comparison. I think there's a place for that.
I don't really get what point the author is trying to make.
I also don't take detailed performance advice from people who can't keep a blog up. Yeah, must be the wrong backend.
If you're really pushing its capabilities then there may be better solutions than MySQL but for bog standard applications and websites there is no alternative as far as I'm concerned.
What other option is so obvious that you can't even name it?
If you're going to be a performance authority about web technology, you should know how to configure the open-source and very well-documented code you are using.
There is no "web technologies" in the article, the term "web" is found only once (!) in the whole text.
Still has no bearing on the veracity of statements made in the article.
How is it that people who have blogs that take 30 seconds to load continue to give performance advice that gets upvoted?
The funny thing is that this blog's performance is based on some cookie. If I reload in Chrome? 2 sec. If I reload in "Incognito Chrome", it's again really slow.
So seriously, just stop with these authoritative blog posts when you don't even know what you're talking about.