Re: Performance Tracker project update

Brooks Davis skrev:
> 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 good, 
>> and the whole operation only takes a few minutes.
> 
> Cool!
> 
>> I have one peculiarity, though. I install python2.5
into the directory 
>> containing the build, and even though the python
version has not changed, I 
>> still get mismatching md5 sums on every .pyo and
.pyc file. Any thoughts on 
>> this?
> 
> I'm not a python guru by any means, but I think .pyc
files probably have 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.

As suggested in other posts, deleting .pyo and .pyc files
gets me down 
to 6MB. Static libraries (.a files) in /usr/lib and
/usr/local/lib still 
have mismatching MD5 sums even though no source code change
warrants 
this. Can I do anything about that? Are static libraries
even needed 
anymore?

Erik
_______________________________________________
freebsd-performancefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-p
erformance
To unsubscribe, send any mail to
"freebsd-performance-unsubscribefreebsd.org"

On Wed, Feb 13, 2008 at 03:46:10PM +0100, Erik Cederstrand
wrote:
> Brooks Davis skrev:
>> 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 
>>> good, and the whole operation only takes a few
minutes.
>> Cool!
>>> I have one peculiarity, though. I install
python2.5 into the directory 
>>> containing the build, and even though the
python version has not changed, 
>>> I still get mismatching md5 sums on every .pyo
and .pyc file. Any 
>>> thoughts on this?
>> I'm not a python guru by any means, but I think
.pyc files probably have 
>> 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.
> 
> As suggested in other posts, deleting .pyo and .pyc
files gets me down to 
> 6MB. Static libraries (.a files) in /usr/lib and
/usr/local/lib still have 
> mismatching MD5 sums even though no source code change
warrants this. Can I 
> do anything about that? Are static libraries even
needed anymore?

I'd suggest checking with cperciva about those for
freebsd-update.
Static libs are mostly not needed these days, but some are.

-- Brooks

Erik Cederstrand wrote:
> Brooks Davis skrev:
>> 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 
>>> good, and the whole operation only takes a few
minutes.
>>
>> Cool!
>>
>>> I have one peculiarity, though. I install
python2.5 into the 
>>> directory containing the build, and even though
the python version 
>>> has not changed, I still get mismatching md5
sums on every .pyo and 
>>> .pyc file. Any thoughts on this?
...
> 
> As suggested in other posts, deleting .pyo and .pyc
files gets me down 
> to 6MB. Static libraries (.a files) in /usr/lib and
/usr/local/lib still 
> have mismatching MD5 sums even though no source code
change warrants 
> this. Can I do anything about that? Are static
libraries even needed 
> anymore?

You may want to look at freebsd-update: I believe it has
some smarts to 
NULL out certain date/time information in files before doing
a 
comparison, so that embedded timestamps don't cause two
otherwise 
identical files to show as different...

At least that is what I recall ... 

--Antony
_______________________________________________
freebsd-performancefreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-p
erformance
To unsubscribe, send any mail to
"freebsd-performance-unsubscribefreebsd.org"