Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 12 Apr 2016 12:37:19 +0200
From:      Sascha Holzleiter <sascha@root-login.org>
To:        Baptiste Daroussin <bapt@freebsd.org>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: pkg-1.7.0 is an order of magnitude slower than pkg-1.6.4
Message-ID:  <b47d8360c0db1fcf9bb7e97273717692@mx01.daemonground.de>
In-Reply-To: <20160407064336.GR49864@ivaldir.etoilebsd.net>
References:  <6DD156C6-C3E1-43BC-8EC5-1ACB16EBFC3E@ellael.org> <20160402124845.GM1128@ivaldir.etoilebsd.net> <05DDCF70-8865-4F1F-A264-3000B8EF5244@ellael.org> <20160407064336.GR49864@ivaldir.etoilebsd.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2016-04-07 08:43, Baptiste Daroussin wrote:
> On Sat, Apr 02, 2016 at 02:59:06PM +0200, Michael Grimm wrote:
>> Baptiste Daroussin <bapt@FreeBSD.org> wrote:
>> >
>> > On Sat, Apr 02, 2016 at 02:42:06PM +0200, Michael Grimm wrote:
>> 
>> >> 26 seconds for 74 ports within a jail and pkg-1.6.4:
>> […]
>> >> 309 seconds for the very same 74 ports within the very same jail and pkg-1.7.0:
>> […]
>> >> Is this an expected slow-down? /usr/ports/UPGRADE and https://svnweb.freebsd.org/ports/head/ports-mgmt/pkg/?view=log are not indicating that behavior.
>> >> But I might have missed something.
>> >>
>> >> Any feedback is highly appriciated, thanks, and regards,
>> >
>> > pkg 1.7 is IO intensive that may explain.
>> 
>> Ok, understood.
>> 
>> JFTR: perl (24s), python27 (44s), and ruby (125s) take the longest 
>> time to reinstall.
>> 
>> > I plan to readd some improvements on this side before 1.8
>> 
>> Good to know, thanks for your feedback.
> 
> Just to follow up on the performance issue, there is a regression that 
> happened
> on FreeBSD 10.3-RELEASE (also HEAD) that causes pkg extraction process 
> to be 10
> times slower as it should. r297626 fixes it in head. We are working on 
> bringing
> that into the 10 branch:
> https://svnweb.freebsd.org/base?view=revision&revision=297626

Thanks for the fix! Will this also be fixed in 10.3-RELEASE? Being 
"stuck" with
the RELEASE branch per policy and looking forward to that kind of 
performance
for the next two years is really painful.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b47d8360c0db1fcf9bb7e97273717692>