Some sites have thousands of items. What's the performance going to be like in that case?

Some sites have thousands of items. What's the performance going to be like in that case?

This issue is specifically is about fetching all items filtered to the provided item name & doesn't fetch all items of a content type from the site. Yes, there could be multiple pages of items with the same name (like in the case of customer issue) & could be low of occurrence given the filter query but I believe we should be fetching all the results from the multiple pages of items despite the performance hit instead of just relying on the first page of items which could lead to unintended consequences. Please let me know of your thoughts on it, Thanks

The point of the bug is that we want to return more than the first page, yes. But what is the performance like? Does it appear to hang?

The point of the bug is that we want to return more than the first page, yes. But what is the performance like? Does it appear to hang?

Not much in the limited testing I performed but it could, depending on the network latency for the requests, another quick option be to bump the default value of TSC_PAGE_SIZE to 500 to reduce the number of API calls for fetching all the pages of items, thoughts?

that does sound like a great quick fix. We could do that and then take a bit more time on this one.

… of items"

This reverts commit e029e22.