2012-06-22 00:10:19 |
Robert Collins |
description |
https://launchpad.net/chromium-project
(Error ID: OOPS-c182f7f94210ede212ae5b835ef993c7) |
https://launchpad.net/chromium-project
(Error ID: OOPS-c182f7f94210ede212ae5b835ef993c7)
SQL time: 12670 ms
Non-sql time: 231 ms
Total time: 12901 ms
Statement Count: 56
count, total, time, savings:
11 9657 877 8780 SQL-main-slave
SELECT Product.answers_usage,
Product.blueprints_usage,
Product.OWNER, Product.active, |
|
2012-06-22 00:14:05 |
Robert Collins |
description |
https://launchpad.net/chromium-project
(Error ID: OOPS-c182f7f94210ede212ae5b835ef993c7)
SQL time: 12670 ms
Non-sql time: 231 ms
Total time: 12901 ms
Statement Count: 56
count, total, time, savings:
11 9657 877 8780 SQL-main-slave
SELECT Product.answers_usage,
Product.blueprints_usage,
Product.OWNER, Product.active, |
https://launchpad.net/chromium-project
(Error ID: OOPS-c182f7f94210ede212ae5b835ef993c7)
SQL time: 12670 ms
Non-sql time: 231 ms
Total time: 12901 ms
Statement Count: 56
served from chaenomeles
count, total, time, savings:
11 9657 877 8780 SQL-main-slave
SELECT Product.answers_usage,
Product.blueprints_usage,
Product.OWNER, Product.active,
Close inspection shows the query is often fast (4-6ms), but the fatal one at the end was 8.5 seconds - either a repeated case of GIL interaction, or a particularly special DB server behaviour.
Possible causes: cross DC interruption, GIL, $? |
|