3 ms·

- Query time: Developers are very squeamish about how long SQL queries take - Payload size: 1000 rows makes the payload huge which adds even more latency - Fr

- Query time: Developers are very squeamish about how long SQL queries take - 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.

Lhiw 5y ago
Nah. It's cause they human and just pick round numbers, 10, 20, 50, 100.
Buttons840 5y ago
> Payload size: 1000 rows makes the payload huge which adds even more latency 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
- Raed667 5y ago
  We went a little bit on that road ended up negotiating 50 rows for desktop and 30 for mobile.
  - mhitza 5y ago
    Sensible UI wise, but if the links are shareable it will just confuse users in the end.
    - Raed667 5y ago
      It was a link behind login, and not expected to be shared. since it's like a list of the user's particular content
quiffledwerg 5y ago
>> 1000 rows makes the payload huge which adds even more latency 1000 rows of json is not huge It’s typically maybe 300k which compresses down to under 50k
marginalia_nu 5y ago
Really none of these things should be a problem. - 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.

Lhiw 5y ago

Nah. It's cause they human and just pick round numbers, 10, 20, 50, 100.

Buttons840 5y ago

> Payload size: 1000 rows makes the payload huge which adds even more latency 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

Raed667 5y ago
We went a little bit on that road ended up negotiating 50 rows for desktop and 30 for mobile.
- mhitza 5y ago
  Sensible UI wise, but if the links are shareable it will just confuse users in the end.
  - Raed667 5y ago
    It was a link behind login, and not expected to be shared. since it's like a list of the user's particular content

quiffledwerg 5y ago

>> 1000 rows makes the payload huge which adds even more latency 1000 rows of json is not huge It’s typically maybe 300k which compresses down to under 50k

marginalia_nu 5y ago

Really none of these things should be a problem. - 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.