summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2011-05-09 22:11:33 -0700
committerZac Medico <zmedico@gentoo.org>2011-05-11 22:20:12 -0700
commite4e1a5dba0589b0bde34abbe5f362d8509192078 (patch)
tree85a9885dbd03b14daed4e2d2e7caa47312cf8ac5
parentd53dfac16cfc793b7f55069bfa49c3544a73bd2a (diff)
downloadportage-e4e1a5dba0589b0bde34abbe5f362d8509192078.tar.gz
portage-e4e1a5dba0589b0bde34abbe5f362d8509192078.tar.bz2
portage-e4e1a5dba0589b0bde34abbe5f362d8509192078.zip
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.
-rw-r--r--pym/_emerge/depgraph.py8
1 files changed, 0 insertions, 8 deletions
diff --git a/pym/_emerge/depgraph.py b/pym/_emerge/depgraph.py
index bd726318b..30085a57f 100644
--- 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):