HarrisonFisk

13 ms·

1.
by HarrisonFisk 3y ago
https://engineering.fb.com/2024/03/06/security/whatsapp-mess...
2.
by HarrisonFisk 3y ago
It wasn’t the top selling car. That seems to be something Elon made up: https://www.autoweek.com/news/industry-news/a44600661/is-tes...
3.
by HarrisonFisk 5y ago
The big tech companies (ie. FANG) all have huge demand for principal+ engineers and know how to scope and support them properly. The size means they have lots of them which reduces the snowflake nature of the role and makes career developm
4.
by HarrisonFisk 5y ago
Direct source is available at: https://github.com/facebook/mysql-5.6 The social graph is indeed stored in MySQL via TAO. A recent white paper about MyRocks is: https://research.fb.com/publications&#x2F
5.
by HarrisonFisk 5y ago
The code is open source: https://github.com/facebook/mysql-5.6
6.
by HarrisonFisk 6y ago
https://en.wikipedia.org/wiki/Anti-Mask_League_of_San_Franci...
7.
by HarrisonFisk 7y ago
Facebook doesn't have engineering titles for exactly this reason.
8.
by HarrisonFisk 10y ago
This is every day at Facebook! https://code.facebook.com/posts/1007323976059780/continuous-...
9.
by HarrisonFisk 10y ago
If you find this book interesting, a good video which talks about Production Engineering at Facebook and talks a bit about Google SRE: https://www.youtube.com/watch?v=ugkkza3vKbc
10.
by HarrisonFisk 12y ago
There is nothing that prevents these from being implemented for PostgreSQL. In fact, they have already done a lot of optimizations that close the gap, such as covering indexes. Before covering indexes, InnoDB was even further ahead of the
11.
by HarrisonFisk 12y ago
Right, PG calls the REDO log the WAL (for most purposes they are the same thing). I did not know that 9.4 can do partial page writes to the WAL now. Guess I will have more reading to do, thanks for pointing it out! A nice blog post by a
12.
by HarrisonFisk 12y ago
(I am a manager of the Data-Perf team at FB which deals with lots of different DB technologies) MySQL (specifically InnoDB) is extremely efficient as a storage backend compared to PostgreSQL. There are a few features that make InnoDB better
13.
by HarrisonFisk 12y ago
There is nothing that precludes public contributions to the project. The important part is that the change be useful to 'webscale' type applications. Prior to this announcement, the only people involved have been these companies
14.
by HarrisonFisk 13y ago
Yes, we are still very active users of MySQL. Most of the primary portions of facebook.com are still served from a backend MySQL system (with lots of caching and many other services involved). Some data is not stored in MySQL, but in othe
15.
by HarrisonFisk 13y ago
Doing compression on the ZFS level is significantly worse than InnoDB compression. InnoDB has a lot of really smart optimizations which make it much better than just zipping things up. Included are the modification log (so you only have to
16.
by HarrisonFisk 13y ago
In addition, when you are dealing with many thousand application servers and many hundred database connections, the database will not end up happy having to maintain > 10k connections. So you will end up needing to add a proxy or connect
17.
by HarrisonFisk 13y ago
Why would the license matter for a kernel module? You know that the linux kernel is also GPL v2 right?
18.
by HarrisonFisk 13y ago
It wasn't for 1B cash, it was 800M cash, 200M Sun stock.
19.
by HarrisonFisk 13y ago
The easiest way is to avoid running into the problem. The main reason the central table space grows is due to rollback segments. To avoid collecting a lot of them there are two tips (in addition to file per table you mentioned): 1. Use mu
20.
by HarrisonFisk 13y ago
This really reminds me a lot of the progression of MySQL. Originally it was used with ISAM/MyISAM and it was pretty popular. Then InnoDB came around and it quickly revolutionized the MySQL world, allowing MySQL to grow to the next lev
21.
by HarrisonFisk 13y ago
When you delete your account, the data is actually removed. As part of the recent privacy audit, the Irish DPC reviewed the account deletion framework and verified that it does indeed work: http://www.dataprotection.ie/docs/21-09-12--Face
22.
by HarrisonFisk 13y ago
Facebook does not sell user data regardless of what you may have heard. See: https://www.facebook.com/help/152637448140583/
23.
by HarrisonFisk 13y ago
The interesting part about this is that MariaDB is only a drop in replacement for MySQL 5.5. MariaDB isn't porting to MySQL 5.6 (which came out last month), instead they are going to try to reimplement all of the functionality from MySQL 5
24.
by HarrisonFisk 13y ago
PostgreSQL doesn't do parallel query.
25.
by HarrisonFisk 14y ago
jemalloc is the new hotness for MySQL. We are using it at Facebook (and I know percona/oracle use it for benchmarks and testing as well). Good benchmark showing the impact of the different options: http://www.mysqlperformanceblog.com/2012
26.
by HarrisonFisk 14y ago
You quote version 3.23, yet talk about subqueries which didn't get added until version 4.1. ONLY_FULL_GROUP_BY was added in 4.0 but only applied to select list columns, the 5.0.23 mentioned above applies to the HAVING clause list not allowi
27.
by HarrisonFisk 14y ago
http://techcrunch.com/2013/01/09/facebook-app-users/
28.
by HarrisonFisk 14y ago
Looking at the benchmarks, something looks wrong in the graphs. For example, for one it looks like they were doing from 0-2M ops for the test. Some of the engines were claimed to do 1M ops per second. That would result in a 2 second ben
29.
by HarrisonFisk 14y ago
Then your slaves will lag really badly while the replication thread keeps stalling on table level locks. InnoDB is faster at reads for most workloads on modern hardware. MyISAM has horrible scalability across multiple CPUs. MariaDB recent
30.
by HarrisonFisk 14y ago
I wonder why they picked MyISAM for MySQL, since basically no one sane is using that anymore. It isn't even the default anymore, so that can't be the excuse. "MyISAM caches index blocks but not data blocks."

More ›