percona | Development repository for the percona cookbook | Infrastructure Automation library

You cannot use curly braces inside curly braces.

MySQL's "Query cache" is internal to MySQL. You still have to perform the SELECT; the result may come back faster if the QC is enabled and usable in the situation.

I don't think the QC is what you are looking for.

The QC is going away in newer versions. Do not plan to use it.

In PHP, consider $_SESSION. I don't know whether it is better than apc_store for your use.

Note also, anything that is directly available in PHP constrains you to a single webserver. (This is fine for small to medium apps, but is not viable for very active apps.)

For scaling, consider storing a small key in a cookie, then looking up that key in a table in the database. This provides for storing arbitrary amounts of data in the database with only a few milliseconds of overhead. The "key" might be something as simple as a "user id" or "session number" or "cart number", etc.

in your config you're giving MySQL 4GB of memory for buffer pools. is that covered with available physical memory? do you actually have > 6GB or more RAM available? if not - please start with decreasing size of innodb buffer pool so the total amount is few GB below available physical memory.

Try to use EXPLAIN to analyze your SELECT DISTINCT query. I bet it will include "Using temporary" and/or "Using filesort". With a large enough result set, these queries will use temporary disk space. But the more frequently you run these queries, the more disk space it uses.

I don't know why you use SELECT DISTINCT * if the rows are already distinct. This may cause the use of a temporary table unnecessarily.

Ideally your query should be:

TL;DR - Nothing, they both are built from the same repository. However, the _/percona images are newer.

The official percona image was last built 4 hours ago (as of writing this), and contains this link to the maintainer's repository:

Notice the hyperlink "Maintained by: Percona", which points to this repository:

• https://github.com/percona/percona-docker

The [Percona Server image] was last built two months ago, and the description contains the following reference to the source code:

This link is the same as the other image, but specifically references a certain directory (which apparently no longer exists, since it returns a 404 Not Found error).

Pulumi has a powerful feature called Transformations which is exactly what you need here(Example). A transformation is a callback that gets invoked by the Pulumi runtime and can be used to modify resource input properties before the resource is created.

I've not tested the code but you should get the idea:

Installing prometheus using the "prometheus-community/kube-prometheus-stack" helm chart could be quite an extensive topic in itself considering the fact that it has a lot of configurable options.

As the helm chart comes with "prometheus operator", we have used PodMonitor and/or ServiceMonitor CRD's as they provide far more configuration options. Here's some documentation around that.

We've installed it with setting "prometheus.prometheusSpec.serviceMonitorSelector.matchLabels" with a label value. Something like this

With your given data in the table:

The first comment was the correct answer "It seems the production server doesn't have a version that supports window functions" After contacting my provider it seems that they still use older versions of MySQL without window functions, thus I will have to change the implementation of ranking system.