Cloud SQL 2nd gen (5.7) very slow after Google Maintenance
After google maintenance on my google cloud instance, on last Saturday night, access to the database from my GAE app is very slow... this is quite obvious on huge tables. Previously I had very good performance, and now terrible. Queries are 10 to 20x slower, which causes error 500 on the app side, after reaching 60s timeouts... also, instance processor is near 100% most of the time, where before was around 20%.
Read/write operations are now insanely higher than before also...
I've already checked table status, optimize relevant tables, drop and rebuild indexes, etc...
It remains the same... can't get it done... actual instance version is 5.7.14-google (Google) - db-n1-standard-1
When checking processes, I can see often these states: 'Sending data' and 'optimizing'... those processes are taking so much time, and are always related to count queries...
For example:
| 298620 | root | cloudsqlproxy~173.194.90.100 | db_name | Query | 7 | Sending data | SELECT COUNT(*) AS `__count` FROM `sms_sms`
WHERE NOT ((`sms_sms`.`origin` = (`sms_sms`.`recipient`) |
| 298636 | root | cloudsqlproxy~74.125.93.164 | db_name | Query | 8 | optimizing | SELECT COUNT(*) AS `__count` FROM `sms_sms`
How to overcome this... it seems that is some problem with the last maintenance update, and I simply cannot do anything to solve this problem...
Any help would be appreciated!
Thanks
google-cloud-sql asked Nov 12 at 10:31
Carlos V.
84
add a comment |
After google maintenance on my google cloud instance, on last Saturday night, access to the database from my GAE app is very slow... this is quite obvious on huge tables. Previously I had very good performance, and now terrible. Queries are 10 to 20x slower, which causes error 500 on the app side, after reaching 60s timeouts... also, instance processor is near 100% most of the time, where before was around 20%.
Read/write operations are now insanely higher than before also...
I've already checked table status, optimize relevant tables, drop and rebuild indexes, etc...
It remains the same... can't get it done... actual instance version is 5.7.14-google (Google) - db-n1-standard-1
When checking processes, I can see often these states: 'Sending data' and 'optimizing'... those processes are taking so much time, and are always related to count queries...
For example:
| 298620 | root | cloudsqlproxy~173.194.90.100 | db_name | Query | 7 | Sending data | SELECT COUNT(*) AS `__count` FROM `sms_sms`
WHERE NOT ((`sms_sms`.`origin` = (`sms_sms`.`recipient`) |
| 298636 | root | cloudsqlproxy~74.125.93.164 | db_name | Query | 8 | optimizing | SELECT COUNT(*) AS `__count` FROM `sms_sms`
How to overcome this... it seems that is some problem with the last maintenance update, and I simply cannot do anything to solve this problem...
Any help would be appreciated!
Thanks
google-cloud-sql asked Nov 12 at 10:31
Carlos V.
84
Same here, and there was an additional update tonight that broke Cloud SQL proxy access to the database.
– nikola
Nov 12 at 22:15
Hi @nikola, the only way i could overcome the issue was to migrate to db-n1-standard-2 instance type, which is more expensive... but for now i'll leave it there till i have some feedback from google... i've reported it here - issuetracker.google.com/issues/119373151
– Carlos V.
Nov 13 at 11:05
add a comment |
After google maintenance on my google cloud instance, on last Saturday night, access to the database from my GAE app is very slow... this is quite obvious on huge tables. Previously I had very good performance, and now terrible. Queries are 10 to 20x slower, which causes error 500 on the app side, after reaching 60s timeouts... also, instance processor is near 100% most of the time, where before was around 20%.
Read/write operations are now insanely higher than before also...
I've already checked table status, optimize relevant tables, drop and rebuild indexes, etc...
It remains the same... can't get it done... actual instance version is 5.7.14-google (Google) - db-n1-standard-1
When checking processes, I can see often these states: 'Sending data' and 'optimizing'... those processes are taking so much time, and are always related to count queries...
For example:
| 298620 | root | cloudsqlproxy~173.194.90.100 | db_name | Query | 7 | Sending data | SELECT COUNT(*) AS `__count` FROM `sms_sms`
WHERE NOT ((`sms_sms`.`origin` = (`sms_sms`.`recipient`) |
| 298636 | root | cloudsqlproxy~74.125.93.164 | db_name | Query | 8 | optimizing | SELECT COUNT(*) AS `__count` FROM `sms_sms`
How to overcome this... it seems that is some problem with the last maintenance update, and I simply cannot do anything to solve this problem...
Any help would be appreciated!
Thanks
google-cloud-sql asked Nov 12 at 10:31
Carlos V.
84
After google maintenance on my google cloud instance, on last Saturday night, access to the database from my GAE app is very slow... this is quite obvious on huge tables. Previously I had very good performance, and now terrible. Queries are 10 to 20x slower, which causes error 500 on the app side, after reaching 60s timeouts... also, instance processor is near 100% most of the time, where before was around 20%.
Read/write operations are now insanely higher than before also...
I've already checked table status, optimize relevant tables, drop and rebuild indexes, etc...
It remains the same... can't get it done... actual instance version is 5.7.14-google (Google) - db-n1-standard-1
When checking processes, I can see often these states: 'Sending data' and 'optimizing'... those processes are taking so much time, and are always related to count queries...
For example:
| 298620 | root | cloudsqlproxy~173.194.90.100 | db_name | Query | 7 | Sending data | SELECT COUNT(*) AS `__count` FROM `sms_sms`
WHERE NOT ((`sms_sms`.`origin` = (`sms_sms`.`recipient`) |
| 298636 | root | cloudsqlproxy~74.125.93.164 | db_name | Query | 8 | optimizing | SELECT COUNT(*) AS `__count` FROM `sms_sms`
How to overcome this... it seems that is some problem with the last maintenance update, and I simply cannot do anything to solve this problem...
Any help would be appreciated!
Thanks
google-cloud-sql google-cloud-sql asked Nov 12 at 10:31
Carlos V.
84
asked Nov 12 at 10:31
Carlos V.
84
edited Nov 12 at 11:03
asked Nov 12 at 10:31
Carlos V.
84
asked Nov 12 at 10:31
Carlos V.
84
asked Nov 12 at 10:31
Carlos V.
84
84
Same here, and there was an additional update tonight that broke Cloud SQL proxy access to the database.
– nikola
Nov 12 at 22:15
Hi @nikola, the only way i could overcome the issue was to migrate to db-n1-standard-2 instance type, which is more expensive... but for now i'll leave it there till i have some feedback from google... i've reported it here - issuetracker.google.com/issues/119373151
– Carlos V.
Nov 13 at 11:05
add a comment |
Same here, and there was an additional update tonight that broke Cloud SQL proxy access to the database.
– nikola
Nov 12 at 22:15
Hi @nikola, the only way i could overcome the issue was to migrate to db-n1-standard-2 instance type, which is more expensive... but for now i'll leave it there till i have some feedback from google... i've reported it here - issuetracker.google.com/issues/119373151
– Carlos V.
Nov 13 at 11:05
Same here, and there was an additional update tonight that broke Cloud SQL proxy access to the database.
– nikola
Nov 12 at 22:15
Same here, and there was an additional update tonight that broke Cloud SQL proxy access to the database.
– nikola
Nov 12 at 22:15
Hi @nikola, the only way i could overcome the issue was to migrate to db-n1-standard-2 instance type, which is more expensive... but for now i'll leave it there till i have some feedback from google... i've reported it here - issuetracker.google.com/issues/119373151
– Carlos V.
Nov 13 at 11:05
Hi @nikola, the only way i could overcome the issue was to migrate to db-n1-standard-2 instance type, which is more expensive... but for now i'll leave it there till i have some feedback from google... i've reported it here - issuetracker.google.com/issues/119373151
– Carlos V.
Nov 13 at 11:05
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fstackoverflow.com%2fquestions%2f53260274%2fcloud-sql-2nd-gen-5-7-very-slow-after-google-maintenance%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fstackoverflow.com%2fquestions%2f53260274%2fcloud-sql-2nd-gen-5-7-very-slow-after-google-maintenance%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
Same here, and there was an additional update tonight that broke Cloud SQL proxy access to the database.
– nikola
Nov 12 at 22:15
Hi @nikola, the only way i could overcome the issue was to migrate to db-n1-standard-2 instance type, which is more expensive... but for now i'll leave it there till i have some feedback from google... i've reported it here - issuetracker.google.com/issues/119373151
– Carlos V.
Nov 13 at 11:05