Stephan Garland

@[email protected]

[Stephan Garland @StephanGarland]

@nateberkopec I would slow all queries more and more every day, until I was given the green light to move the DB to bare metal as Codd intended.

[Stephan Garland @StephanGarland]

@AdamRackis @tylermac @bravelyjake Sure – so they can boost executive compensation and shareholder profits.

[Stephan Garland @StephanGarland]

@mipsytipsy With all due respect, you absolutely did (ISBN-13: 978-1491925942).

[Stephan Garland @StephanGarland]

@NielsHoven I had this experience at Samsung. Sitting in on meetings where PhD chemists were discussing chip yields, pulling up various charts at dizzying rates, absorbing them, and moving on before I had read the axes.

I consider myself decently intelligent, but that was on another level.

[Stephan Garland @StephanGarland]

@FranckPachot The fact that ClusterVolumeIOPs is actually “IO/300 seconds” will never fail to infuriate me. If I wanted a 5 minute average, I’d ask for that.

[Stephan Garland @StephanGarland]

@fasterthanlime Wait until he learns about utf8mb4.

[Stephan Garland @StephanGarland]

@jeremycole Do you have any specific gripes against it? Genuinely curious; I know it changed, but I have no idea about any cons it brings.

[Stephan Garland @StephanGarland]

@JamesRLandrum @DhravyaShah Sure, but you said “few ms.” 54 is far beyond any definition of “few” I’ve ever heard.

Agreed that sites don’t necessarily have to have multiple round trips, but unless you can fit everything into initcwnd – 14.6 KB by default – there are at least two, plus handshake.

[Stephan Garland @StephanGarland]

@JamesRLandrum @DhravyaShah Even if data traveled at the speed of light (it doesn’t), and there was 0 overhead from processing (there isn’t), a round-trip 5000 mile distance would take 54 msec.

Very interested to see your math.

[Stephan Garland @StephanGarland]

@vvsevolodovich @rmoff There is nothing wrong with this stack in the slightest. I would take Django over literally every other ORM. MySQL is more performant than Postgres if you know how to work with it, rather than against it (also, it takes effectively zero ongoing maintenance, unlike PG).

[Stephan Garland @StephanGarland]

@joshmanders @samlambert And network: people always forget that EC2s have network bandwidth limits which are confusing as hell, and it absolutely is possible to saturate the smaller – medium ones. That’s not something really anyone would expect to happen, and yet. Surprise!

[Stephan Garland @StephanGarland]

@joshmanders @samlambert K8s on cloud (which is most) brings other challenges that people might not be aware of: network and disk performance limits. If you use the default StorageClass, last I checked it’s gp3. Maybe that’s good enough, but maybe for bigger DBs it isn’t (at least, not with defaults).
/2

[Stephan Garland @StephanGarland]

@m1ru1 @ChShersh @_atlj I don’t know how to say this other than your average Haskell dev is ridiculously more skilled than your average JS dev. I am neither, to be clear.

Haskell is such a niche language that if you learn it, you must be innately curious and interested in computers. That pays dividends

[Stephan Garland @StephanGarland]

@blbraner @dhh Do you think people are running their own DCs? There is a very small handful of companies that do that.

Rent rack space in a colo. Done.

[Stephan Garland @StephanGarland]

@CoderciseYT @kenwheeler

[Stephan Garland @StephanGarland]

I simultaneously want to and do not want to find out why large loop performance (and apparently other things) has been steadily declining in Python since 3.11. I also have a sinking feeling that it's not going to be fixed, and I'll be stuck at 3.11.

https://t.co/NEsZEujzac

[Stephan Garland @StephanGarland]

@yacineMTB False. I read it offline to better absorb the information, and then go try out some of the concepts I want to explore more, referencing the book as necessary.

Also, black-on-white is flaring, and inverse looks odd when there’s just a huge expanse of space. Paper reads better.

[Stephan Garland @StephanGarland]

@ClassicGamerTWR @thdxr I've seen a mid-sized MySQL instance happily running with 1000 connections. I can't say the same about Postgres.

Don't take this as a slam on Postgres; I like it plenty, it's just worse at connection handling. Which is why a pooler is practically required.

[Stephan Garland @StephanGarland]

@ClassicGamerTWR @thdxr No RDBMS like it, sure, but again my only assertion is that Postgres is uniquely bad at it. There's a reason that the RDS default for `max_connections` parameter works out to 12/ram_size_mib for MySQL, and 9/ram_size_mib per Postgres.

/1