From: grarpamp <grarpamp@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Scalability issues
Date: Fri, 27 Jul 2012 15:37:27 -0400 [thread overview]
Message-ID: <CAD2Ti2-+W7cnxQe22_5iBvXMjeL_wYB=LnsPGF4zxpMR1BeJkQ@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgT9ZSTj-yR4DQ_+8XTeGTTEJbo22LLmyxSn2sJM3jAbig@mail.gmail.com>
> I'd love to know precisely what Bitcoin is doing thats making your
> machine so unhappy... but your configuration is uncommon for bitcoin
> nodes in many distinct ways so it's not clear where to start.
That's why I posted the details of the machine so interested people
could duplicate it if they are working in these areas. Once I'm on new
hardware and playing around I, also, may find some discoveries.
I have no doubt that 'common' is windows seven on core2duo
without ecc and no crypto or hashing for the disk :)
next prev parent reply other threads:[~2012-07-27 19:37 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 [this message]
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='CAD2Ti2-+W7cnxQe22_5iBvXMjeL_wYB=LnsPGF4zxpMR1BeJkQ@mail.gmail.com' \
--to=grarpamp@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
/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