ikonic89

5 ms·

1.
Windows and Containers(bitesizedengineering.com)
2 points by ikonic89 4y ago|0 comments
2.
A Guide To Becoming a Reader (and reading 30 books in a year)(unstructed.tech)
52 points by ikonic89 5y ago|17 comments
3.
MySQL optimizations on large scale – tips, tricks and WTFs(ikonicscale.com)
9 points by ikonic89 6y ago|0 comments
4.
by ikonic89 6y ago
Sorry for the late reply :) Looks like we have between 20T and 25T of data, combined across all MySQL databases. And somewhere in the region between 60B and 80B records. Edit: this is just for data that's used all the time. Almost not
5.
by ikonic89 6y ago
I can break it down quickly, here: - Scaling web servers is much easier. Queries are (mostly, on a single host) executed one after another, so if one is slow, you suddenly have a queued of queries waiting to be executed. The goal is to ex
6.
by ikonic89 6y ago
We did test Vitess couple of years ago, just decided not to go with it. There were a lot of reasons for that, maybe a topic for another post.
7.
by ikonic89 6y ago
Yeah, I can agree with that. You really need to know what you're doing. We have benchmarks for most of such "micro-optimizations", though now we can know how things are going to behave before we even make them, just from the
8.
by ikonic89 6y ago
Glad you liked it :)
9.
by ikonic89 6y ago
You are 100% correct. We expected to see a drop in activity after the interest in show reduced, but we're still hitting records day after day. Crazy.
10.
A bit on scaling chess.com's database(unstructed.tech)
246 points by ikonic89 6y ago|90 comments