Is there a page speed penalty for large, segmented HubDB tables?
解決
We present several hundred application notes to our visitors, organized in 20 topic segments/pages using 20 HubDB tables (kudos HubSpot for this utility!). This leaves me 20 tables to maintain, but if I were to combine all ~500 line-items into one table for use across each of these 20 pages, calling only the relevant line items for each page, would there be a page-speed penalty or would the server only be burdened for the requested entries?
Is there a page speed penalty for large, segmented HubDB tables?
解決
This happens server-side, so the actual render is dynamic based on the request. Similar to code-splitting in webpack, if you're only requesting rows 20-25 of the table that's all that'll be returned.
Of course there's a limit to everything, that's why HubDB has a limit of 10,000 rows. For a 500 line table, there shouldn't be any page speed penalty for this - it's atually one of the benefits of HubDB!
Is there a page speed penalty for large, segmented HubDB tables?
解決
This happens server-side, so the actual render is dynamic based on the request. Similar to code-splitting in webpack, if you're only requesting rows 20-25 of the table that's all that'll be returned.
Of course there's a limit to everything, that's why HubDB has a limit of 10,000 rows. For a 500 line table, there shouldn't be any page speed penalty for this - it's atually one of the benefits of HubDB!
