On Mon, Jun 8, 2009 at 8:24 PM, Nagy Gabor<
ngaba@...> wrote:
> *: I started to work on the implementation of mixed target list, and I
> realised that the most annoying "difference" is that PKG_FROM_CACHE
> packages are not duplicated, so they are mustn't be freed (the new
> _alpm_pkg_free_trans should be used), but PKG_FROM_FILE packages must be
> freed. How much memory can we spare by not duplicating sync packages
> (not calling _alpm_pkg_dup when adding them to transaction target)? The
> whole base repo is <0.5 MB atm. Does this hack "worth"? With the old
> behaviour, implementing this idea (and so FS#3492 and FS#5798) would be
> really nice. With the new behaviour it would not. (And I don't really
> like the need for _alpm_pkg_free_trans neither.)
>
Yeah it looks quite painful to handle.
You should have a careful look at this article :
http://www.toofishes.net/blog/valgrind-330-and-new-massif/It would be nice if you could run these experiments yourself on the
current codebase, and check the difference is indeed <0.5MB.
_______________________________________________
pacman-dev mailing list
pacman-dev@...
http://www.archlinux.org/mailman/listinfo/pacman-dev
