No server-side processing vs Server-side processing
No server-side processing vs Server-side processing
Hello DataTables Community,
I have questions about the server load usage with DataTables:
1) From how many records it is better to switch to a server-side processing? 100 entries ? 1000 entries ?
2) What is the best mode (server-side processing/no server-side) to minimize MySQL ressource usage ?
It is better for MySQL performance to SELECT a large amount of rows in ONE TIME from the table without ORDER/LIMIT/WHERE clause, or SELECT small amount of rows but with ORDER/LIMIT/WHERE clause ?
3) Is there a way to change the mode (server-side processing/no server-side) depending on the amount of records to display?
Exemple: records<100 no server-side processing, records >= 100 server-side processing
Cordially,
Nicolas.
I have questions about the server load usage with DataTables:
1) From how many records it is better to switch to a server-side processing? 100 entries ? 1000 entries ?
2) What is the best mode (server-side processing/no server-side) to minimize MySQL ressource usage ?
It is better for MySQL performance to SELECT a large amount of rows in ONE TIME from the table without ORDER/LIMIT/WHERE clause, or SELECT small amount of rows but with ORDER/LIMIT/WHERE clause ?
3) Is there a way to change the mode (server-side processing/no server-side) depending on the amount of records to display?
Exemple: records<100 no server-side processing, records >= 100 server-side processing
Cordially,
Nicolas.
This discussion has been closed.
Replies
2. Depends upon your table, and how many rows there are. Also on if you want to spread the hit over time or do it all up front. The answer to 1 is also relevant I think.
3. You would need to know ahead of the initialisation if you want to use SSP or not. It cannot be changed on the fly.
Allan