From: Zac Medico <zmedico@gentoo.org>
Date: Tue, 10 May 2011 05:11:33 +0000 (-0700)
Subject: depgraph: don't clear vardbapi cache in _load_vdb
X-Git-Tag: v2.2.0_alpha33~15
X-Git-Url: http://git.tremily.us/?a=commitdiff_plain;h=d124a775634706eb954fa70116de8367f165d1d5;p=portage.git

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 7b1940b5a..22a603e81 100644
--- a/pym/_emerge/depgraph.py
+++ b/pym/_emerge/depgraph.py
@@ -551,14 +551,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):