From: "Alex Barcelo" <alex@betarho•net>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] About hardware accelerators advantages for full-node (not mining)
Date: Mon, 13 Jul 2015 12:55:14 +0000 [thread overview]
Message-ID: <c872dcb5d7538526a251829ec9d90afb@owncloud.betarho.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1080 bytes --]
I am searching for guidance and opinion in the subject's matter. I will begin with my use case, too see whether my ideas makes sense or not.
I have a Jetson TK1[1], which is a GPU (CUDA) powered development board. I thought that it may be a power-efficient device (in bitcoin environment), and thought about having it as a full-node. Either as a public full-node, if it makes sense, or a local full-node, to allow my PCs to perform relay onto the bitcoind in the Jetson. My idea is to run a bitcoind daemon on the Jetson as a node with high performance-per-watt (also cheap and repurposable). A pure-CPU implementation of bitcoind will clog the CPU
I assume that there are a bunch of heavy-compute highly-parallel functions which could be "outsourced" to a GPU. I may want to fork and/or contribute on that. However, maybe I am speaking nonsense. I have more background on parallel programming than my knowledge on bitcoin protocol. So, before coding a complete mess, I wanted to hear some opinions on the idea/configuration.
[1] https://developer.nvidia.com/jetson-tk1
[-- Attachment #2: Type: text/html, Size: 1320 bytes --]
next reply other threads:[~2015-07-13 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 12:55 Alex Barcelo [this message]
2015-07-13 13:47 ` Tier Nolan
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=c872dcb5d7538526a251829ec9d90afb@owncloud.betarho.net \
--to=alex@betarho$(echo .)net \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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