Re: Finding slowdowns in pkg_install (continuations of previous threads)

Tim Kientzle wrote: The following blog post has all of my commentary on the results I have: . I tried to unroll strcmp a bit by checking for the first character of the >

Re: Finding slowdowns in pkg_install (continuations of previous threads)

The following blog post has all of my commentary on the results I have: . I tried to unroll strcmp a bit by checking for the first character of the > command, then run strc

Re: Finding slowdowns in pkg_install (continuations of previous threads)

Tim Kientzle wrote: 4. CSV files available at: http://students.washington.edu/youshi10/posted/atk-results.tgz. I've posted HTML results of the interpreted spreadsheet on . I'll provide commentary tomorrow after I get some sleep. I think the sec

Re: Finding slowdowns in pkg_install (continuations of previous threads)

4. CSV files available at: http://students.washington.edu/youshi10/posted/atk-results.tgz. I've posted HTML results of the interpreted spreadsheet on . I'll provide commentary tomorrow after I get some sleep. I think the second one should be:

Re: Finding slowdowns in pkg_install (continuations of previous threads)

Garrett Cooper píše v so 14. 07. 2007 v 04:04 -0700: > I've posted HTML results of the interpreted spreadsheet on > . I'll provide commentary > tomorrow after I get some sleep. Nothing on that URL. -- Pav Lucistnik <[EMAIL PROTECTED]>

Re: Finding slowdowns in pkg_install (continuations of previous threads)

Garrett Cooper wrote: Garrett Cooper wrote: Tim Kientzle wrote: -I tried ... buffering ... the +CONTENTS file parsing function, and the majority of the time it yielded good results One approach I prototyped sometime back was to use libarchive in pkg_add as follows: * Open the arch

Re: Finding slowdowns in pkg_install (continuations of previous threads)

Garrett Cooper wrote: Tim Kientzle wrote: -I tried ... buffering ... the +CONTENTS file parsing function, and the majority of the time it yielded good results One approach I prototyped sometime back was to use libarchive in pkg_add as follows: * Open the archive * Read +CONTENTS

Re: Finding slowdowns in pkg_install (continuations of previous threads)

Tim Kientzle wrote: -I tried ... buffering ... the +CONTENTS file parsing function, and the majority of the time it yielded good results One approach I prototyped sometime back was to use libarchive in pkg_add as follows: * Open the archive * Read +CONTENTS directly into memory (i

Re: Finding slowdowns in pkg_install (continuations of previous threads)

-I tried ... buffering ... the +CONTENTS file parsing function, and the majority of the time it yielded good results One approach I prototyped sometime back was to use libarchive in pkg_add as follows: * Open the archive * Read +CONTENTS directly into memory (it's guaranteed to alwa

Re: Finding slowdowns in pkg_install (continuations of previous threads)

Tim Kientzle wrote: I'm currently running a gamut of tests (500 tests, per package -- 128 total on my server), and outputting all data to CSV files to interpret later, using another Perl script to interpret calculated averages and standard deviations. Excellent! Much-needed work. Usin

Re: Finding slowdowns in pkg_install (continuations of previous threads)

I'm currently running a gamut of tests (500 tests, per package -- 128 total on my server), and outputting all data to CSV files to interpret later, using another Perl script to interpret calculated averages and standard deviations. Excellent! Much-needed work. Using basic printf(2)'s w

Re: Finding slowdowns in pkg_install (continuations of previous threads)

Garrett Cooper wrote: I'm currently running a gamut of tests (500 tests, per package -- 128 total on my server), and outputting all data to CSV files to interpret later, using another Perl script to interpret calculated averages and standard deviations. Using basic printf(2)'s with cloc

Finding slowdowns in pkg_install (continuations of previous threads)

I'm currently running a gamut of tests (500 tests, per package -- 128 total on my server), and outputting all data to CSV files to interpret later, using another Perl script to interpret calculated averages and standard deviations. Using basic printf(2)'s with clock_gettime(2) I have det