Files
aptly/cmd
Andrey Smirnov 021b8c4cff Lower memory usage for aptly db cleanup
This is not a complete fix, but the easiest first step.

During `db cleanup`, aptly is loading every repo/mirror/... into memory,
and even though each object is processed only once, collection holds
a reference to all the loaded objects, so they won't be GC'd until
process exits.

CollectionFactory.Flush() releases pointers to collection objects,
making objects egligble for GC.

This is not a complete fix, as during iteration we could have tried
to release a link to every object being GCed and that would have
helped much more.
2018-07-20 01:04:51 +03:00
..
2017-03-23 01:51:08 +03:00
2014-04-05 16:11:19 +04:00
2017-03-23 01:51:08 +03:00
2014-07-28 19:17:21 +04:00
2017-03-23 01:51:08 +03:00
2014-07-28 19:17:21 +04:00
2017-03-23 01:51:08 +03:00
2017-03-23 01:51:08 +03:00
2017-03-23 01:51:08 +03:00
2017-05-04 23:00:13 +03:00
2014-08-16 14:14:56 +00:00