Fred van Dijk

The challenge is that the serializers are in multiple modules and were written for sometimes different purposes. Maybe this issue is better solved in plone.exportimport, which is a rewritten version...

Example to fix this in 6b422016ceb7bb7b515e53952b476330f9c3dba0 . But I don't think this is the right way to solve these edge cases, will create another issue

The tests were only added 9-10 days ago, some time after the 1.0 release was made. If you want to test the latest improvements you'll have to use an interim/dev...

Hi Dylan, Thanks for starting this issue. I promised Philip to create to separate issues 2 weeks ago, but work, flue 'light' and PloneConf preparation got into the way. I...

I ran into this issue today where writing a resulting 7.2Gb File.json to the server directory (var) took almost 16Gb memory. 8Gb was not enough. With some help from @mauritsvanrees...

I have run into one other issue with supporting a lot of content: On import 'something' is generating temp files in /tmp for every single File that is imported. And...

Still have to create a PR with my streaming export fixes.... :-$

@pbauer See https://github.com/collective/collective.exportimport/tree/yield_export with the small modifications need to make the export content use a generator. This avoids collecting all json in a python string, which ballooned the python process...

For these blob sizes inline blobs are out of the question anyway. What we discussed previously: I noticed exponential time when importing larger Files. My import with a 7Gb Files.json...

@Rudd-O This is indeed the work around, but I think I also mentionned TMPDIR in the comment you are referencing. However, this was in June and I think 1-2 months...