depgraph: don't clear vardbapi cache in _load_vdb

Most of the memory is probably held on the heap by the installed
package instances anyway, and the cache is useful for being inherited
by subprocess in MergeProcess.

diff --git a/pym/_emerge/depgraph.py b/pym/_emerge/depgraph.py
index bd726318b5534f8d425923ef04f33ea752dc23b7..30085a57feb05c7000b6b2277b966cf01dcc5d37 100644 (file)
--- a/pym/_emerge/depgraph.py
+++ b/pym/_emerge/depgraph.py
@@ -357,14 +357,6 @@ class depgraph(object):
                                        vardb.aux_get(pkg.cpv, [])
                                        fakedb.cpv_inject(pkg)
 
-                               # Now that the vardb state is cached in our FakeVartree,
-                               # we won't be needing the real vartree cache for awhile.
-                               # To make some room on the heap, clear the vardbapi
-                               # caches.
-                               self._frozen_config._trees_orig[myroot
-                                       ]["vartree"].dbapi._clear_cache()
-                               gc.collect()
-
                self._dynamic_config._vdb_loaded = True
 
        def _spinner_update(self):