This is more a limit of client side plugin. All your search is loaded by Fuzzy plugin to be able to run on them. With new WU pricing, we don’t recommend using Fuzzy search plugin. Better to use search input if possible instead. But Jedi could help you get best of both world.
I do believe @listme you could benefit from the Data Jedi Plugin to help with reducing WUs for such large data sets.
In terms of the searching and filtering, I’m not sure what your use of the fuzzy search is for, but generally, a need to just do a simple match, the fuzzy search wouldn’t really be necessary. As far as I understand, the reasons for using fuzzy search is more for finding matching items based on misspellings, or partial matches, so you might find improvement by simply not using fuzzy search and just use legacy bubble data structuring approach. I used fuzzy search plugin 7 years ago, and uninstalled it and have never bothered to try again, because it was crashing the page. I just decided to use an input element and do a search or used search box element.
When I did a test with 51,200 items on the page using the Hybrid Data Structuring approach the Data Jedi plugin helps make super simple to implement, I could just use the native Bubble search constraints on those things and didn’t have any issue with the speed of the search. But, there was a bit of a lag time on the page load due to such a large dataset, which no matter which approach is used will happen on such large datasets, and likely dependent on the users device. My computer apparently is not a computer well suited for such large tasks to be processed on the device, but it still searches and matches fine.