misc/firestuff
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Google MySQL team is hiring

Browse Source
This commit is contained in:
Ian Gulliver
2019-04-15 03:56:57 +00:00
parent dae78cb7f9
commit fdae596016
5 changed files with 23 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
2011-12-09-the-dangers-of-max-connections.html
View File

@@ -5,7 +5,7 @@
<p>We have a database that's drastically scaling up its query rate from many different clients. This typically means more client jobs and more parallelization across connections, so the first limit we hit is max_user_connections (in the mysql.user table), which we use to provide isolation between runaway users/jobs. We increase that, and we eventually start hitting server-level max_connection limits. We increased that in an emergency push last night, and several hours later performance fell off a cliff.</p>
<p>SHOW PROCESSLIST showed tons of processes in "Opening tables" and "closing tables" state. Our InnoDB IO stats had dropped dramatically; we clearly weren't making significant progress actually answering queries. A quick search turned up a Percona post about this, which pointed to table_cache. A quick look at SHOW VARIABLES LIKE 'table_cache' showed 91. Our config has this set to 2048; something had clearly gone wrong.</p>
<p>SHOW PROCESSLIST showed tons of processes in "Opening tables" and "closing tables" state. Our InnoDB IO stats had dropped dramatically; we clearly weren't making significant progress actually answering queries. A quick search turned up a <a href="http://www.mysqlperformanceblog.com/2006/11/21/opening-tables-scalability/">Percona post</a> about this, which pointed to <a href="http://dev.mysql.com/doc/refman/5.0/en/table-cache.html">table_cache</a>. A quick look at SHOW VARIABLES LIKE 'table_cache' showed 91. Our config has this set to 2048; something had clearly gone wrong.</p>
<p>One hint was the error log message:</p>

10
2012-03-09-google-mysql-team-is-hiring.html Normal file
View File

@@ -0,0 +1,10 @@
<!--# set var="title" value="Google MySQL team is hiring" -->
<!--# set var="date" value="March 9, 2012" -->
<!--# include file="include/top.html" -->
<p>Do you know MySQL inside and out? Do you have experience running it production? Have you dared to look at the code? Maybe even patched it? Google's MySQL team would love to speak to you. We're hiring several software engineers in Mountain View, CA, USA to primarily work on MySQL server improvements, contributing to Google's <a href="http://code.google.com/p/google-mysql/">open source MySQL branch</a>. In addition to feature work, Google MySQL developers work closely with operations-focused engineers tracking down bugs and solving tricky performance problems, at truly enormous scale.</p>
<p>Sound interesting? Email <a href="mailto:flamingcow@google.com">flamingcow@google.com</a>.</p>
<!--# include file="include/bottom.html" -->

1
index.html
View File

@@ -20,6 +20,7 @@
<li>2016-Feb-15: <a href="2016-02-15-cable-modem-channel-party.html">Cable modem channel party</a></li>
<li>2016-Feb-01: <a href="2016-02-01-how-to-enrage-your-cable-modem.html">How to enrage your cable modem</a></li>
<li>2016-Feb-01: <a href="2016-02-01-hall-of-2-4-ghz-shame-2016-edition.html">Hall of 2.4 GHz Shame, 2016 Edition</a></li>
<li>2012-Mar-09: <a href="2012-03-09-google-mysql-team-is-hiring.html">Google MySQL team is hiring</a></li>
<li>2011-Dec-09: <a href="2011-12-09-the-dangers-of-max-connections.html">The dangers of max_connections</a></li>
<li>2011-Nov-29: <a href="2011-11-29-converting-subselects-to-joins-part-2.html">Converting subselects to joins, part 2</a></li>
<li>2011-Nov-29: <a href="2011-11-29-safer-data-changes.html">Safe(r) data changes</a></li>

10
markdown/2012-03-09-google-mysql-team-is-hiring.md Normal file
View File

@@ -0,0 +1,10 @@
<!--# set var="title" value="Google MySQL team is hiring" -->
<!--# set var="date" value="March 9, 2012" -->
<!--# include file="include/top.html" -->
Do you know MySQL inside and out? Do you have experience running it production? Have you dared to look at the code? Maybe even patched it? Google's MySQL team would love to speak to you. We're hiring several software engineers in Mountain View, CA, USA to primarily work on MySQL server improvements, contributing to Google's [open source MySQL branch](http://code.google.com/p/google-mysql/). In addition to feature work, Google MySQL developers work closely with operations-focused engineers tracking down bugs and solving tricky performance problems, at truly enormous scale.
Sound interesting? Email [flamingcow@google.com](mailto:flamingcow@google.com).
<!--# include file="include/bottom.html" -->

1
markdown/index.md
View File

@@ -19,6 +19,7 @@
1. 2016-Feb-15: [Cable modem channel party](2016-02-15-cable-modem-channel-party.html)
1. 2016-Feb-01: [How to enrage your cable modem](2016-02-01-how-to-enrage-your-cable-modem.html)
1. 2016-Feb-01: [Hall of 2.4 GHz Shame, 2016 Edition](2016-02-01-hall-of-2-4-ghz-shame-2016-edition.html)
1. 2012-Mar-09: [Google MySQL team is hiring](2012-03-09-google-mysql-team-is-hiring.html)
1. 2011-Dec-09: [The dangers of max_connections](2011-12-09-the-dangers-of-max-connections.html)
1. 2011-Nov-29: [Converting subselects to joins, part 2](2011-11-29-converting-subselects-to-joins-part-2.html)
1. 2011-Nov-29: [Safe(r) data changes](2011-11-29-safer-data-changes.html)