Facebook
Twitter
S
surfichris
Guest
Hi,
Whilst not technically a bug - I'm throwing this in this forum as it's a scaling issue.
It appears with the introduction of custom ports, along side piped access logs means that for every single hit to the web server (that's being logged), there are 5 database queries that are executed. Whilst these are obviously going to hit a MySQL cache (and some just get/set variables), this causes unnecessary work on the database server.
I believe the querying is done to determine the https port (as indicated by the last query). Can't this be cached somewhere on the file system to prevent the superfluous querying?
For every single hit:
Whilst not technically a bug - I'm throwing this in this forum as it's a scaling issue.
It appears with the introduction of custom ports, along side piped access logs means that for every single hit to the web server (that's being logged), there are 5 database queries that are executed. Whilst these are obviously going to hit a MySQL cache (and some just get/set variables), this causes unnecessary work on the database server.
I believe the querying is done to determine the https port (as indicated by the last query). Can't this be cached somewhere on the file system to prevent the superfluous querying?
For every single hit:
Code:
45791 Connect admin@localhost on psa
45791 Query set foreign_key_checks=0
45791 Query SHOW VARIABLES LIKE 'version'
45791 Query SELECT val FROM misc WHERE param='mysql41_compatible'
45791 Query SET NAMES binary
45791 Query select val from misc where param='https_port'
45791 Quit
