Skip to main content
Bounty Ended with 25 reputation awarded by CommunityBot
deleted 18 characters in body
Source Link
middlelady
  • 553
  • 1
  • 6
  • 17

General speaking yes for read-only applications (until MySQL 5.7, it's deprecated since version 8.0), it enables identicalequal SELECTs to return data extremely fast if identical calls are already stored in cache. You should consider that:

  • Only identicalexact same clauses can benefit from the cache engine (no spaces, no comments, no actual differences in WHERE expressions);
  • If you are updating often the table, you will not benefit much of it, since the queries get invalidated, and the invalidation algorithms can also reduce performance, in some cases.

Excellent alternatives to improve performance are:

I think also if you combine those with a good web server like NGINX or Apache2 and aan HTTP accelerator like Varnish you can fly.

As I know, these are also the best current practices but I might have ignored something else, please share it in case.

General speaking for read-only applications (until MySQL 5.7, it's deprecated since version 8.0), it enables identical SELECT to return data extremely fast if identical calls are stored in cache. You should consider that:

  • Only identical clauses can benefit from the cache engine (no spaces, no comments, no actual differences in WHERE expressions);
  • If you are updating often the table, you will not benefit much of it, since the queries get invalidated, and the invalidation algorithms can reduce performance, in some cases.

Excellent alternatives to improve performance are:

I think also if you combine with a good web server like NGINX or Apache2 and a HTTP accelerator like Varnish you can fly.

As I know, these are also the best current practices but I might have ignored something else, please share it in case.

General speaking yes for read-only applications (until MySQL 5.7, it's deprecated since version 8.0), it enables equal SELECTs to return data extremely fast if identical calls are already stored in cache. You should consider that:

  • Only exact same clauses can benefit from the cache engine (no spaces, no comments, no actual differences in WHERE expressions);
  • If you are updating often the table you will not benefit much of it, since the queries get invalidated, and the invalidation algorithms can also reduce performance, in some cases.

Excellent alternatives are:

I think also if you combine those with a good web server like NGINX or Apache2 and an HTTP accelerator like Varnish you can fly.

As I know, these are also the best current practices but I might have ignored something, please share it in case.

Source Link
middlelady
  • 553
  • 1
  • 6
  • 17

General speaking for read-only applications (until MySQL 5.7, it's deprecated since version 8.0), it enables identical SELECT to return data extremely fast if identical calls are stored in cache. You should consider that:

  • Only identical clauses can benefit from the cache engine (no spaces, no comments, no actual differences in WHERE expressions);
  • If you are updating often the table, you will not benefit much of it, since the queries get invalidated, and the invalidation algorithms can reduce performance, in some cases.

Excellent alternatives to improve performance are:

I think also if you combine with a good web server like NGINX or Apache2 and a HTTP accelerator like Varnish you can fly.

As I know, these are also the best current practices but I might have ignored something else, please share it in case.