Bug #4866
Updated by Davide Pesavento about 5 years ago
`ndnputchunks` ndnputchunks needs over **3x the memory** as the size of the content file that is served. uploaded. For example: - 100MB file -> needs 336MB RAM - 300MB file -> needs 980MB RAM The required memory is completely freed up after closing ndnputchunks, so it's not about caching inside NFD. I wonder what explains this inefficiency? Moreover, is it possible to have ndnputchunks store files on the disk, in order to save memory?