public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: steve <steve@mistfpga.net>
To: "Michael Grønager" <gronager@mac.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Scalability issues
Date: Mon, 23 Jul 2012 16:54:33 +0100	[thread overview]
Message-ID: <500D73B9.5030806@mistfpga.net> (raw)
In-Reply-To: <A428177D-62AD-4712-9053-47B7ED5DBC84@mac.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Michael,

On 23/07/2012 10:00, Michael Grønager wrote:
> I get a full blockchain from scratch in 45 minutes on my laptop,
> /M
> 
Hang on a sec, in 45 minutes you can download the entire chain from
the genesis block?

I have been doing extensive testing in this area and would love to
know what is special about your setup (I have never had the entire
chain in under 12 hours, infact it is normally closerto 24.) I have an
extensive setup of test machines, everything from e4300 to phenom2x6
to i5's.

as an example on an amd e-450 with 4gb ram, and approx 3gb/s internet
connection it took 2 hours to sync the last 5 days.

Maybe i am missing something important...

Any additional information that you could provide to help me with
testing would be really appreciated.

cheers,

steve

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJQDXO4AAoJEFvEB9dQFvtQxdcH/ieqQkyDCg8mKeOa6CqsWaS6
fhoeny3Ke2b/CsvhYmsThCvntN9volIqR2CTn5tkHiVwG9OmlxyHZcNpN0ZTHhK5
lsfLap/Y0QpiysXpV4Bu7Z4Hwp9jnhOP74TshT305r2pX6EGXPQ0CrlHqlIry/X/
vNcunUclliou+KjL7EHcY50GH5wDpqJAjlNyF97Lj9YiPrAC9vahGwWdxkbCYtG+
KUuWGBKMMdHuMAgcQh7nI9q0WT3k/gzRQtuC2kf+v0wvQhaGlTVkku4uanhpuw4p
99blRF3/SfWimGuQgsm6wT3Y7dk+z8MFHLb6XGPxmgV9+gF+TWNczfU3GRzfcXw=
=CQkI
-----END PGP SIGNATURE-----



  parent reply	other threads:[~2012-07-23 16:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-22 22:37 [Bitcoin-development] Scalability issues 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
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 [this message]
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=500D73B9.5030806@mistfpga.net \
    --to=steve@mistfpga.net \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gronager@mac.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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