zlacker

[parent] [thread] 7 comments
1. maccar+(OP)[view] [source] 2023-08-30 20:18:42
Airbnb is a great example of a terrible experience that just keeps getting worse. It makes my M1 Mac, my 32 core workstation and my top of the line android device chug.
replies(1): >>rozap+i5
2. rozap+i5[view] [source] 2023-08-30 20:38:10
>>maccar+(OP)
The shininess of the engineering blog and the actual product seem to be completely disconnected. All the major players (Airbnb, Instagram, Facebook, Twitter) go on about all these often genuinely impressive perf optimizations, but if you actually try the product they're borderline unusable. It's pretty clear that the blogging is just a clout chasing exercise, but the cognitive dissonance is still palpable.
replies(2): >>maccar+dg >>umanwi+3k
◧◩
3. maccar+dg[view] [source] [discussion] 2023-08-30 21:31:19
>>rozap+i5
I think Airbnb is the worst offender by far though. Instagram, Facebook and Twitter (just using your examples) operate very dynamic applications at a global scale. AirBnB is a crud app with almost no dynamic content other than the booking system. According to the first site I saw online, they process 6 bookings per second, which I could handle on literally anything with an internet connection. Of all of them, its the one I understand the least.
replies(1): >>steve_+8n
◧◩
4. umanwi+3k[view] [source] [discussion] 2023-08-30 21:52:25
>>rozap+i5
From experience at Facebook: there are extremely good people working on performance and making heroic optimizations. The blog content is real. However, these are necessary precisely because the politics and culture of the organization make it impossible to avoid bloat that accumulates faster than the small minority of perf-conscious folks can improve things.
◧◩◪
5. steve_+8n[view] [source] [discussion] 2023-08-30 22:11:57
>>maccar+dg
I thought this sounded way too low but the most generous figure I can find is 12 per second in 2022. What the hell? I thought it would be more. Should I have thought that? I guess not.
replies(1): >>sa46+Wz
◧◩◪◨
6. sa46+Wz[view] [source] [discussion] 2023-08-30 23:46:07
>>steve_+8n
6 bookings per second at $200 per booking is $103M processed per day.

Each booking likely represents dozens to hundreds of requests. Then, for every visit resulting in a booking there’s probably hundreds of non-booking visits.

replies(2): >>maccar+mB1 >>lopken+o92
◧◩◪◨⬒
7. maccar+mB1[view] [source] [discussion] 2023-08-31 09:27:30
>>sa46+Wz
> 6 bookings per second at $200 per booking is $103M processed per day.

I don't doubt that they don't prcess a lot of money - that's besides the point.

They're a cookie cutter CRUD app (that happens to process a lot of money) that takes _hundreds_ of requests and 12 seconds to load on a 32 core workstation with a gigabit fibre internet connection. They have no business writing a blog on performance engineering.

◧◩◪◨⬒
8. lopken+o92[view] [source] [discussion] 2023-08-31 13:14:43
>>sa46+Wz
If your CRUD app's booking endpoint internally fans out to 100s of requests, you're doing something extremely wrong and/or you've dug yourself into microservice hell.
[go to top]