On Mon, Jan 13, 2014 at 5:49 PM, Alec Warner <anta...@gentoo.org> wrote: [...] > > This is not meant to imply that portage is always fast; there are plenty of > other modules (such as the aforementioned backtracking) that can take a long > time to find solutions. That is partially why you see Tomwij turning off > that feature. It is helpful for users cause it can automatically find > solutions for users that are otherwise unsolvable (and thus avoids the user > having to find a solution to the depgraph manually.)
Yeah, correct. But it would be nice if Portage backtrack_depgraph() would memoize (asynchronously serializing to disk, for instance) partial results for later use. AFAIR, last time I checked, it wasn't doing that. Also, it would be nice if the aux_db cache of the vdb could be stored in a sqlite3 db rather than in RAM. This dict is consuming a huge cut of memory for little reason (a single vdb.dbapi.match() can eat 100MB of RAM). We know how Python deals with freed memory... Sigh... > > -A > >> >> >> -- >> Luis Ressel <ara...@aixah.de> >> GPG fpr: F08D 2AF6 655E 25DE 52BC E53D 08F5 7F90 3029 B5BD > > -- Fabio Erculiani
