Datareader deserialization buffers: is there a way to release the buffers ?

Hello,

I understand that the property "dds.data_writer.history.memory_manager.fast_pool.pool_buffer_max_size" configure the size of each buffer of the pool of deserialization buffers (datareader and datawriter) and there is one buffer per topic instance.

I my case, datawriters are such that there is lot of instances (more than 100 000) which represent micro-states of the system and one single sample per instance. I use TRANSIANT, RELIABLE and KEEP_ALL.

I noticed that the deserialization buffers cost a lot of memory on the readers side even if these datareaders use ContentFilteredTopic (to exclude most of the instances).

Note that the CFT is working only on reader side because I have to use asynchronous publisher at writer side (it saves memory if CFT on writer side is effective, I checked)

I deduce that when CFT is only on reader side, serialization buffers are created for each instances and never released, even if the instances are rejected.

Is there a way to release these buffers ?

(note that I don't matter about performance issues at this step).

Thanks.

Boris.