You might want to check out listingbott.com by @johnrush.me

Looks very neat!

Interesting, why is that the case?

Most of the time I'd do smth like `flex-col md/lg:flex-row` and perhaps also center on xs screens. Things usually look nicer centered on small screens.

I have to go to sleep lol

Also, around 10ms is spent rendering SVGs 🙃 I can LRU cache these calls.

I'm not gonna do scientific benchmarks for now, but when profiling locally in production mode, it seems that it takes 4-5ms to render one element (MBP M1), and half of it is rendering the dropdown.

And the AR records are all loaded on the first element, so there's a "view penalty" from it as well?

No sleeping 😅 The Phlex part is embedded in a Rails view (the whole collection is a single Phlex component though).

It dances with Rails a bit. The dropdown is... a Rails partial that renders a ViewComponent, because I haven't yet migrated all to Phlex. I can profile and see what the bottleneck is.

The view that takes ~100ms to render is actually Phlex.

It renders a list of entities and has quite a bit of markup because each elem has a dropdown menu.

Here's what it looks like. The collection is uncached.

So I rebooted Intel and it works much better now. Still slower than AMD but 1.5x, not 4x 😅

Yeah it's a shared one

OK, I'm onto something. Changed my CPU from Intel to AMD and it starts looking reasonable now.

I'm gonna switch back to Intel once more - perhaps either loud neighbour or smth wrong with physical server?

Or is AMD really THAT MUCH FASTER?!

really nothing interesting here.

Works faster than production locally.

Hetzner is 2x slow as Render even though it has 4vCPU, while Render has 0.5 CPU for web and 0.5 cpu for postgres 😬

Gonna look further...

Good question! Gonna check it out in an hour

Its probably either a loud neighbour on the cpu or I really f'ed something up when upgrading Rails from 7.2 to 8.0 🤔🤔🤔

The DB is on the same Hetzner machine as my app

Same view on render.com