- Payload size: 1000 rows makes the payload huge which adds even more latency
- Frontend performance: More modest machines will struggle to render very large dynamic tables of rich content.
- Payload size: 1000 rows makes the payload huge which adds even more latency
- Frontend performance: More modest machines will struggle to render very large dynamic tables of rich content.
- Presenting your bread-and-butter data shouldn't require complex joins or expensive queries. If it does, you are doing something wrong.
- You can serve the text of a thousand page book in just a few hundred Kb. If your payload size is large, then I guarantee it's not the text on the page that's at fault.
- Likewise, no computer (not even one from 1996) will struggle rendering plain HTML. Any performance problems your website has are problems you've added yourself.
I recently built a feature at BigCo. Like all our stuff, we have the default page size be a meager 10 rows, so as not to upset anyone. Because everything is always 10 rows. However, the frontend is hard coded to always request page sizes of 1000, which results in a payload of less than 100kb. Or at least, that was the plan until an "architect" spotted it and got upset because 1000 rows is clearly beyond the pale. SMH
1000 rows of json is not huge
It’s typically maybe 300k which compresses down to under 50k