It would make sense to use the external indexer (consists on all nodes in umbraco) or maybe create a custom index with your document type, assuming all nodes are of the same document type, and then just include into the index the properties that you need.
Then you can just search the index for those nodes and print them onto the page quite fast. As i said, if you include all of your required properties into the index, you wont need to ping the cache / DB or any additional data.
If that does not improve the performance to a satisfactory level, you can always lazy load more nodes as the user scrolls the page.
What's the best practice for listing large number of nodes in one page
Hi,
Can you advice for the best practices for listing around 300 news with their text and images in page .
I have concerns about the loading performance.
and what do you think if I use Examine to achieve that ?
Please advice.
Thanks
It would make sense to use the external indexer (consists on all nodes in umbraco) or maybe create a custom index with your document type, assuming all nodes are of the same document type, and then just include into the index the properties that you need.
Then you can just search the index for those nodes and print them onto the page quite fast. As i said, if you include all of your required properties into the index, you wont need to ping the cache / DB or any additional data.
If that does not improve the performance to a satisfactory level, you can always lazy load more nodes as the user scrolls the page.
Who would want to load such a big page in their browser?
Why don't you want to use paging?
is working on a reply...