Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SuceW-0006kq-8x for bitcoin-development@lists.sourceforge.net; Fri, 27 Jul 2012 04:59:52 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.161.175 as permitted sender) client-ip=209.85.161.175; envelope-from=gmaxwell@gmail.com; helo=mail-gg0-f175.google.com; Received: from mail-gg0-f175.google.com ([209.85.161.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1SuceV-00040c-IG for bitcoin-development@lists.sourceforge.net; Fri, 27 Jul 2012 04:59:52 +0000 Received: by ggnp4 with SMTP id p4so2837170ggn.34 for ; Thu, 26 Jul 2012 21:59:46 -0700 (PDT) MIME-Version: 1.0 Received: by 10.66.79.8 with SMTP id f8mr2499760pax.81.1343365185618; Thu, 26 Jul 2012 21:59:45 -0700 (PDT) Received: by 10.68.59.6 with HTTP; Thu, 26 Jul 2012 21:59:45 -0700 (PDT) In-Reply-To: References: Date: Fri, 27 Jul 2012 00:59:45 -0400 Message-ID: From: Gregory Maxwell To: grarpamp Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.1 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.5 AWL AWL: From: address is in the auto white-list X-Headers-End: 1SuceV-00040c-IG Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] Scalability issues 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: Fri, 27 Jul 2012 04:59:52 -0000 On Fri, Jul 27, 2012 at 12:20 AM, grarpamp wrote: > Update: this class of machine just became useless for bitcoin. > When blk0002.dat was created to store more blocks, all forward > progress processing blocks turned into losing ground by 20 or so > a day. Guessing both datfiles were being accessed at once resulting > in disk based overload. I've not seen any other mentions of crypto > in this thread so I'm not sure how well new hardware would perform. > Going shopping I guess. I now have an 1.8 ghz p3 celeron (128k cache) which should be substantially slower than your machine, running vintage 2.6.20 linux. Unfortunately I forgot to turn on timestamp logging so I don't know how long it took to sync the chain, but it was less than two days as that was the span between when I checked on it. It's staying current just fine. Again, I encourage you to investigate your software configuration.