Boost objects get bloated with owner and user objects
From original comment related to Iterator::hydrate()
method...
If we make a call to expire the boost it's at this point that we bloat the boost object with the hydrated owner and user objects - which will likely never be used.
Should the Manager / Repository unset those objects before syncing?
In this case the owner and entity objects are many times the size of the dehydrated boost object.
Edited by Guy Thouret