mysql 8 information_schema.processlist -> correct approach to cache it?
I have a high concurrency mysql 8.0 server.
Thousands of tasks happen per second (up to a million rows per second read in average)
In some of the tasks that can be very performance intense I have an emergency switch to prevent the database queue from overflowing.
I read the number of processes (sometimes specific ones) from information_schema.processlist and if they exceed a certain value the task is skipped until the database is back in time.
So much so good, that worked perfectly fine in mysql 5.7 and before, but in mysql 8.0 they removed the query cache which might be the reason why it can not deliver such performance anymore.
In my case the server quickly is overflown with these SELECTS.
So I decided to run a background task that refreshes a table every second with a dump of the processlist.
I am using Innodb as MEMORY has more blocking issues.
This is the syntax I run every second:
processlist is "LIKE information_schema.processlist but I've changed the Info blob to a varchar"
BEGIN;
truncate table processlist;
replace into processlist SELECT ID,USER,HOST,DB,COMMAND,TIME,STATE,LEFT(INFO,1024) AS INFO FROM information_schema.processlist WHERE Command != 'Sleep';
COMMIT;
I am using a transaction to prevent race conditions and just truncate + replace into.
However I am not sure if this is the best solution to populate a "mirror" table.
So my question is: is this a good approach (especially not sure what truncate might mean on performance) ? Any ideas how to do this better ?
mysql mysql-8.0
asked 2 mins ago
JohnJohn
1357
add a comment |
I have a high concurrency mysql 8.0 server.
Thousands of tasks happen per second (up to a million rows per second read in average)
In some of the tasks that can be very performance intense I have an emergency switch to prevent the database queue from overflowing.
I read the number of processes (sometimes specific ones) from information_schema.processlist and if they exceed a certain value the task is skipped until the database is back in time.
So much so good, that worked perfectly fine in mysql 5.7 and before, but in mysql 8.0 they removed the query cache which might be the reason why it can not deliver such performance anymore.
In my case the server quickly is overflown with these SELECTS.
So I decided to run a background task that refreshes a table every second with a dump of the processlist.
I am using Innodb as MEMORY has more blocking issues.
This is the syntax I run every second:
processlist is "LIKE information_schema.processlist but I've changed the Info blob to a varchar"
BEGIN;
truncate table processlist;
replace into processlist SELECT ID,USER,HOST,DB,COMMAND,TIME,STATE,LEFT(INFO,1024) AS INFO FROM information_schema.processlist WHERE Command != 'Sleep';
COMMIT;
I am using a transaction to prevent race conditions and just truncate + replace into.
However I am not sure if this is the best solution to populate a "mirror" table.
So my question is: is this a good approach (especially not sure what truncate might mean on performance) ? Any ideas how to do this better ?
mysql mysql-8.0
asked 2 mins ago
JohnJohn
1357
add a comment |
I have a high concurrency mysql 8.0 server.
Thousands of tasks happen per second (up to a million rows per second read in average)
In some of the tasks that can be very performance intense I have an emergency switch to prevent the database queue from overflowing.
I read the number of processes (sometimes specific ones) from information_schema.processlist and if they exceed a certain value the task is skipped until the database is back in time.
So much so good, that worked perfectly fine in mysql 5.7 and before, but in mysql 8.0 they removed the query cache which might be the reason why it can not deliver such performance anymore.
In my case the server quickly is overflown with these SELECTS.
So I decided to run a background task that refreshes a table every second with a dump of the processlist.
I am using Innodb as MEMORY has more blocking issues.
This is the syntax I run every second:
processlist is "LIKE information_schema.processlist but I've changed the Info blob to a varchar"
BEGIN;
truncate table processlist;
replace into processlist SELECT ID,USER,HOST,DB,COMMAND,TIME,STATE,LEFT(INFO,1024) AS INFO FROM information_schema.processlist WHERE Command != 'Sleep';
COMMIT;
I am using a transaction to prevent race conditions and just truncate + replace into.
However I am not sure if this is the best solution to populate a "mirror" table.
So my question is: is this a good approach (especially not sure what truncate might mean on performance) ? Any ideas how to do this better ?
mysql mysql-8.0
asked 2 mins ago
JohnJohn
1357
I have a high concurrency mysql 8.0 server.
Thousands of tasks happen per second (up to a million rows per second read in average)
In some of the tasks that can be very performance intense I have an emergency switch to prevent the database queue from overflowing.
I read the number of processes (sometimes specific ones) from information_schema.processlist and if they exceed a certain value the task is skipped until the database is back in time.
So much so good, that worked perfectly fine in mysql 5.7 and before, but in mysql 8.0 they removed the query cache which might be the reason why it can not deliver such performance anymore.
In my case the server quickly is overflown with these SELECTS.
So I decided to run a background task that refreshes a table every second with a dump of the processlist.
I am using Innodb as MEMORY has more blocking issues.
This is the syntax I run every second:
processlist is "LIKE information_schema.processlist but I've changed the Info blob to a varchar"
BEGIN;
truncate table processlist;
replace into processlist SELECT ID,USER,HOST,DB,COMMAND,TIME,STATE,LEFT(INFO,1024) AS INFO FROM information_schema.processlist WHERE Command != 'Sleep';
COMMIT;
I am using a transaction to prevent race conditions and just truncate + replace into.
However I am not sure if this is the best solution to populate a "mirror" table.
So my question is: is this a good approach (especially not sure what truncate might mean on performance) ? Any ideas how to do this better ?
mysql mysql-8.0
mysql mysql-8.0
asked 2 mins ago
JohnJohn
1357
asked 2 mins ago
JohnJohn
1357
asked 2 mins ago
JohnJohn
1357
asked 2 mins ago
JohnJohn
1357
asked 2 mins ago
JohnJohn
1357
1357
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f227909%2fmysql-8-information-schema-processlist-correct-approach-to-cache-it%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f227909%2fmysql-8-information-schema-processlist-correct-approach-to-cache-it%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
