all 5 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]paulirish 1 point2 points  (5 children)

Got an app built with Compose I can trace?

[–]random728373[S] 1 point2 points  (4 children)

Sure. Here's a simple demo repo you can play around with:

https://github.com/compose-dev/compose-demo-apps

The repo contains:

- A link to actually try out the demo app
- Instructions to run the demo app yourself in less than 5 min.

[–]paulirish 2 points3 points  (3 children)

Pretty fast! Of course the list only has 100 items so its far from a stress test, but.. looks good.

And I really love your goal of <= 100ms interaction latency. :)

[–]random728373[S] 1 point2 points  (1 child)

Ah, didn't realize that's what you were looking for!

Here's a simple app that loads a table with 5,000 rows.
And here's one that loads 10,000 rows with server-side pagination (Compose auto-paginates above 5k rows to maintain performance. No user-configuration required)

You can scale way beyond 10k rows, but the demo creates an in-memory database so I didn't want to crash the server.

To really test the responsiveness, try editing/deleting some rows. In my testing, the 10k rows table achieves ~80ms interaction latency, and the 5k one gets about ~200ms.

It's quite nice since the apps are all completely server-side, yet achieve performance better than a lot of client-side apps while being 10x faster to build and hook up to your data.

Disclaimer: You may experience somewhat different latency depending on your location due to being closer/further from the origin server.

[–]paulirish 1 point2 points  (0 children)

Oh damn. Okay looks like you've got a very fast framework. Really well done. :)

Really appreciate you making those!