I like the product a lot and wanted it to use it to display extracts from a database. This has about 4500 rows and 45 columns.
My experience of using Create a table linked to an existing data source. and uploading this as an Excel file is that it runs too slowly, taking up to a minute to load a sample of about 10 rows and 4 columns.
I prefer this option because when we update the database every 3 months we can replace the source file and the table will update without us having to recreate each table from scratch.
If I were to load the Excel sheet into an SQL database, would it load any quicker?
Yes, of course it would be faster. This is due to the fact that database tables (SQL query based tables) are server-side tables, meaning those tables fetch only those rows needed on the page at the exact moment.
Tables linked to an existing data source fetch all the rows, output the entire table to the front-end all at once, and then split it into pages using JavaScript; all data processing (page switching, sorting, filtering) is done on the client’s computer by JavaScript. While this works great for relatively small tables, once a table gets bigger, the page also gets larger. Consequently, page generation and load time will also increase correspondingly, and sorting, filtering, or page switching will take more time. So, for larger data sets (more than 2000-3000 rows, and in some installations more than 500 rows), the “usual” wpDataTables will work more slowly, and for really large data sets (10 000 rows and more) the page can crash completely.
Hi there,
I like the product a lot and wanted it to use it to display extracts from a database. This has about 4500 rows and 45 columns.
My experience of using Create a table linked to an existing data source. and uploading this as an Excel file is that it runs too slowly, taking up to a minute to load a sample of about 10 rows and 4 columns.
I prefer this option because when we update the database every 3 months we can replace the source file and the table will update without us having to recreate each table from scratch.
If I were to load the Excel sheet into an SQL database, would it load any quicker?
Many thanks M
Hello Martin
Thank you for your purchase.
Yes, of course it would be faster. This is due to the fact that database tables (SQL query based tables) are server-side tables, meaning those tables fetch only those rows needed on the page at the exact moment.
Tables linked to an existing data source fetch all the rows, output the entire table to the front-end all at once, and then split it into pages using JavaScript; all data processing (page switching, sorting, filtering) is done on the client’s computer by JavaScript. While this works great for relatively small tables, once a table gets bigger, the page also gets larger. Consequently, page generation and load time will also increase correspondingly, and sorting, filtering, or page switching will take more time. So, for larger data sets (more than 2000-3000 rows, and in some installations more than 500 rows), the “usual” wpDataTables will work more slowly, and for really large data sets (10 000 rows and more) the page can crash completely.
Kind Regards,
Aleksandar Vuković
[email protected]
Rate my support
wpDataTables: FAQ | Facebook | Twitter | Instagram | Front-end and back-end demo | Docs
Amelia: FAQ | Facebook | Twitter | Instagram | Amelia demo sites | Docs | Discord Community
You can try wpDataTables add-ons before purchasing on these sandbox sites:
Powerful Filters | Gravity Forms Integration for wpDataTables | Formidable Forms Integration for wpDataTables | Master-Detail Tables