vbresults
Well-known member
As I understand it, query results are presently buffered (read into memory all at once). As traffic goes up this eats more RAM.
More ram = more expensive server bill. The proposal is to read them row-by-row with XHR.
If implemented, then admins could downgrade their servers and save money, yet support the same (or more) traffic.
This is the age of JS, and pages could be pre-rendered the classic way for spiders and older clients.
I can't see anything but benefits for both small and big boards.
Edit: This may also make way for merging core and add-on queries results, then separating them on the client side using event listeners. This can open a few doors in terms of performance and efficiency.
More ram = more expensive server bill. The proposal is to read them row-by-row with XHR.
If implemented, then admins could downgrade their servers and save money, yet support the same (or more) traffic.
This is the age of JS, and pages could be pre-rendered the classic way for spiders and older clients.
I can't see anything but benefits for both small and big boards.
Edit: This may also make way for merging core and add-on queries results, then separating them on the client side using event listeners. This can open a few doors in terms of performance and efficiency.
Last edited:
Upvote
1