From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RscSZ-0008UV-Lx for bitcoin-development@lists.sourceforge.net; Wed, 01 Feb 2012 15:50:59 +0000 X-ACL-Warn: Received: from 2508ds5-oebr.0.fullrate.dk ([95.166.54.49] helo=mail.ceptacle.com) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1RscST-0006sw-Pq for bitcoin-development@lists.sourceforge.net; Wed, 01 Feb 2012 15:50:59 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.ceptacle.com (Postfix) with ESMTP id B4308167D716; Wed, 1 Feb 2012 16:50:47 +0100 (CET) X-Virus-Scanned: amavisd-new at ceptacle.com Received: from mail.ceptacle.com ([127.0.0.1]) by localhost (server.ceptacle.private [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6bp-NQj-4f8r; Wed, 1 Feb 2012 16:50:46 +0100 (CET) Received: from [10.0.1.28] (2508ds5-oebr.0.fullrate.dk [95.166.54.49]) by mail.ceptacle.com (Postfix) with ESMTPSA id E2D03167D709; Wed, 1 Feb 2012 16:50:46 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1251.1) Content-Type: text/plain; charset=iso-8859-1 From: =?iso-8859-1?Q?Michael_Gr=F8nager?= In-Reply-To: Date: Wed, 1 Feb 2012 16:50:46 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: Gregory Maxwell X-Mailer: Apple Mail (2.1251.1) X-Spam-Score: 0.8 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.8 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RscST-0006sw-Pq Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Announcement: libcoin X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2012 15:50:59 -0000 Hi Gregory, I played with the database sync as well to get further speedups, but in = the latest version I could only get about 1% extra from this.=20 In the Satoshi client there is a bunch of sleeps and mutexes (put in = there with great generosity) for making threads run smoother and to = avoid deadlock I guess. The big change in speed came from moving from the threading based setup = to the async based setup, so I think these are the culprit. Further, as = I also write somewhere in the wiki. I can measure that 50% of the time = is consumed in verify, so there is not much left to optimize now. = Actually, Berkeley DB does a quite decent job in caching reads so not = even a cache should help. Cheers, M On 01/02/2012, at 15:59, Gregory Maxwell wrote: > On Wed, Feb 1, 2012 at 9:18 AM, Michael Gr=F8nager = wrote: >> The libcoin/bitcoind client downloads the entire block chain 3.5 = times faster than the bitcoin/bitcoind client. This is less than 90 = minutes on a modern laptop! >=20 > Very interesting. Do you know where this speedup came from? It's not > typical for straight refactors that don't change datastructures and > the like to see such big speedups. >=20 > I see you have commented out code that disables fsync, which was my > first guess since I get big speedups from doing similar things. Michael Gronager, PhD Director, Ceptacle Jens Juels Gade 33 2100 Copenhagen E Mobile: +45 31 45 14 01 E-mail: gronager@ceptacle.com Web: http://www.ceptacle.com/