Hi @ktamb sorry for not explaining!
What I suggested with the previous comment is that you download that .zip, which contains a on-development version of Tainacan, go to your WordPress plugins page → “Add new” , click on Send/upload and from there install the new version.
The WP-Cron is how background processes are managed. In Tainacan they are used for three things: Importers, Exporters and Bulk Editing operations. You can disable it safely if you are not going to need any of these three.
I’m not familiar with how the APM runs its performance check, but you will need some good willing from your web host if he is already asking to remove Tainacan just due to that. The point is that, Tainacan does and will be doing a lot of stuff in your server, and that is not necessarily an issue, it is mainly the plugin doing the job to which you need it. The Items List with the faceted search is a complex UI, and having its filters and advanced search features available comes with its cost to the database and host.
But I still think there might be other reasons for having your issue, we have numerous use cases in different hosting platforms that are not hitting PHP threads limits without a good reason. If you ever point us to specific things to investigate, we will see if there is an improvement, I promise that. The other topic that I mentioned, for example, was the case of a user who identified a performance bottleneck in a JS library that we use to render progressive loading on images. That was an hypothesis that have good arguments and I was able to identify the issue and solve (I hope so, we’re testing it). The WP Cron is a solid argument and if proven the root cause we could even investigate ways to offer disabling the features related to it more easily in the UI. But all in all, Tainacan will do more things than, say, UpdraftPlus, a plugin that only runs its job from time to time to generate a backup. Do you agree?
Specifically about the URL params, if you read them, you’ll see they all are needed to build the current state of the items list. The define order, which metadata are shown, pagination and later which filters are applied. It is a really dynamic content so it is not something that is cached as an HTML in the page, the component actually refreshes itself internally via JS every time you change something (requests are done via REST API).