From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: Performance regression on NFS with new manifest version Date: Wed, 09 Aug 2017 22:39:50 +0200 Message-ID: <873790o4q1.fsf@elephly.net> References: Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52658) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dfXlr-0008D9-DV for guix-devel@gnu.org; Wed, 09 Aug 2017 16:40:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dfXlq-0000iV-3l for guix-devel@gnu.org; Wed, 09 Aug 2017 16:40:03 -0400 In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Roel Janssen Cc: guix-devel Hi Roel, > Looking into the manifests ($GENERATION_15/manifest and > $GENERATION_16/manifest), I noticed that generation 15 uses manifest > version 2, and generation 16 uses manifest version 3. > > What has changed, so that it takes a lot longer to run the same command > as before? (this is probably disk-related, because that is a known > cause for trouble on network-mounted stores..) Commit 55b4715fd4c03e46501f123c5c9bc6072edf12a4 bumped the manifest version to 3. The goal was to represent propagated inputs as manifest entries so that we can anticipate conflicts from propagated inputs and refuse to build a profile when there would be conflicts. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC https://elephly.net