Date: Fri, 08 Feb 2008 20:42:01 +0100 From: Ivan Voras <ivoras@freebsd.org> To: freebsd-performance@freebsd.org Subject: Re: Performance Tracker project update Message-ID: <foibab$a2g$1@ger.gmane.org> In-Reply-To: <20080208151756.GA35423@lor.one-eyed-alien.net> References: <4796C717.9000507@cederstrand.dk> <20080123193400.N63024@fledge.watson.org> <4797A245.7080202@cederstrand.dk> <20080123202433.E63024@fledge.watson.org> <4797A802.8060509@FreeBSD.org> <47A0BFE7.4070708@cederstrand.dk> <20080130190000.GA18333@lor.one-eyed-alien.net> <47AC15A5.5020009@cederstrand.dk> <20080208151756.GA35423@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig81991AAF532A8F150E7388EA Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Brooks Davis wrote: > On Fri, Feb 08, 2008 at 09:41:09AM +0100, Erik Cederstrand wrote: >> I finally got around to testing this, and with a combination of mtree = >> comparing md5 hashes, bsdiff compacting changed files and hardlinking = >> unchanged files I get a reduction in size from 256MB to 10MB. Pretty g= ood,=20 >> and the whole operation only takes a few minutes. >=20 > Cool! >=20 >> I have one peculiarity, though. I install python2.5 into the directory= =20 >> containing the build, and even though the python version has not chang= ed, I=20 >> still get mismatching md5 sums on every .pyo and .pyc file. Any though= ts on=20 >> this? >=20 > I'm not a python guru by any means, but I think .pyc files probably hav= e data > about the .py they are generated from because there's some sort of > auto-generation available. It may be possible to not store them at all= and > just generate them before you use them or add some magic build flags to= cause > them to store some sort of cooked values. I'm not sure where the .pyo = files > come from. =2Epyc/.pyo contain at least the timestamp of the original .py file and=20 maybe a compilation timestamp. You can indeed safely delete all .pyc and = =2Epyo files and forget about them - the only penalty will be slightly=20 slower application startup times as the .py files are compiled every time= =2E =2Epyo are optimized version of .pyc. AFAIK currently the optimizations=20 are not worth it. --------------enig81991AAF532A8F150E7388EA Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHrLCKldnAQVacBcgRApcHAKDUh3GqcnCJvofW7mJHodntV53gFgCZAXU7 MTI1AHbajqvRU4vBjMWRBz0= =OxFf -----END PGP SIGNATURE----- --------------enig81991AAF532A8F150E7388EA--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?foibab$a2g$1>