While playing ATM10, my initial storage solution is Sophisticated Storage with Integrated Dynamics. As my storage network has grown over time I've had some performance issues and have worked with the ID team to help improve performance of it as much as possible.

In one of the reports that initially looked like an Integrated Dynamics issue, they believe it's starting to hit the limits of ID accessing third-party storage systems via the regular item handler API. They feel they've taken it as far as they can with the current capabilities and suggest that to get better performance it would require Sophisticated Storage to implement their Common Capabilities slotless item handler API.

I'm opening this issue to see if there's any chance of that happening, or if there's anything else that could collaboratively be done to improve performance?

Thank you.

@Lonestar0011 this issue is more of a proposal to implemen SlotLessItemhandler cap because the cause in the original is really the size of the storage system and number of the slots causing issues that could be partially solved by using slot less implementation but that one is specific to Integrated Dynamics and may not even help in your scenario even if you used that mod.
So I feel this one would deserve separate issue created for it, but I would also like to get a bit more info on the setup because it seems that about 80% of the time is spent getting block entities from the world which leads me to believe that either there's some issue with another mod inserting a lot of logic in there, or your setup is much more extensive than just a few sophisticated storage blocks attached to controller.

I also encountered a similar performance issue relating to Sophisticated Storage interacting with a different mod.
Im playing ATM9 and use AE2 for as my Storage System. I have a few Sophisticated Storage chest/barrel on Storages buses via a storage controller.
In my Spark report for Sophiticated Core is at 26%

In my Spark Report for Applied Energistics the Import/Export Category is at 13% with alot of it tracable to Sophisticated Core

Not sure if this is the same issue but it may very well be.
I hope this helps.