From e4e1a5dba0589b0bde34abbe5f362d8509192078 Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Mon, 9 May 2011 22:11:33 -0700 Subject: 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. --- pym/_emerge/depgraph.py | 8 -------- 1 file changed, 8 deletions(-) (limited to 'pym') 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): -- cgit v1.2.3-1-g7c22