From: grarpamp <grarpamp@gmail•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Scalability issues
Date: Fri, 27 Jul 2012 00:20:12 -0400 [thread overview]
Message-ID: <CAD2Ti28snGOZn9mCSALZ341TNCex23zxKHCKYztnMK3cF=jaTQ@mail.gmail.com> (raw)
In-Reply-To: <CAD2Ti2_Pz9-SsHP49+6MKnM0er9zdAaFKDQaOgqDpju1_igd_g@mail.gmail.com>
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.
next prev parent reply other threads:[~2012-07-27 4:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 22:37 grarpamp
2012-07-23 7:23 ` Raphael NICOLLE
2012-07-23 7:35 ` Gregory Maxwell
2012-07-23 9:00 ` Michael Grønager
2012-07-23 15:11 ` grarpamp
[not found] ` <CAAS2fgREzk_dU0ie+YvDdRwKcTk6tk_i=a2Bb74w9uF=EwYhGA@mail.gmail.com>
2012-07-23 22:33 ` grarpamp
2012-07-27 4:20 ` grarpamp [this message]
2012-07-27 4:59 ` Gregory Maxwell
2012-07-27 5:59 ` grarpamp
2012-07-27 6:03 ` Luke-Jr
2012-07-27 6:28 ` grarpamp
2012-07-27 6:56 ` Gregory Maxwell
2012-07-27 19:37 ` grarpamp
2012-07-27 8:53 ` Andreas Petersson
[not found] ` <CAPg+sBjpqqxL_GxYc+8Ry7DcXMkouO9bYi5VqOyEjj_5s0x06Q@mail.gmail.com>
2012-07-27 9:59 ` Pieter Wuille
2012-07-27 19:26 ` grarpamp
2012-07-23 15:54 ` steve
2012-07-24 8:25 ` Michael Grønager
2012-07-24 9:18 ` Mike Hearn
2012-07-24 19:56 ` steve
2012-07-25 9:45 ` Michael Grønager
2012-07-25 14:24 ` steve
2012-07-23 22:50 ` Aidan Thornton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAD2Ti28snGOZn9mCSALZ341TNCex23zxKHCKYztnMK3cF=jaTQ@mail.gmail.com' \
--to=grarpamp@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox