Performance issues at 3DXML exchange collaboration

Not 100% sure, if using right community for this topic but found some article of @FK on this topic in here, I relate to.

https://r1132100503382-eu1-3dswym.3dexperience.3ds.com/#community:38/post:ke_o-8W-RNynA8yjYRZJ-Q

 

We do recognize some significant performance issues at the data exchange by using 3DXML, we did not have before. When trying to export even smaller assemblies with approximate 300 objects, it takes 3-4 hours for the the export to be performed (using Exchange Management app) and the resulting 3DXML has more than 1 GB size and is now rejected for import due to size limitation.

By this conclusion, we were trying to export and import an older but very large customer assembly to a test tenant, we had imported 2 years ago to our main tenant without any issue. This time, the resulting file size exceeded the allowed import size by far and the export took close to a whole work day.

Since FD03, there is this new "Split" function, that can be activated for the export, that may solve the size limitation problem, but export/import time will be the same and we did not manage to import all the resulting 3DXML into a common structure.

Due to these excessive export/import times, we are also not able to do further investigations, as any test does block the 3DEXPERIENCE client for several hours to a certain tenant.

Regarding the 3DXML data exchange strategy with delegation for collaboration between 2 tenants, we do see problems to propagate this method as it will take our customer hours to exchange even modification rights.

So my question: does someone else also face such issues? Is there an option or setting, we are missing, that may speed up the export/import process?