From: Christian Grothoff <christian@grothoff.org>
To: Sree Harsha Totakura <sreeharsha@totakura.in>
Cc: guix-devel@gnu.org
Subject: Re: GNUnet build failure on mips64el
Date: Sat, 22 Feb 2014 12:41:56 +0100 [thread overview]
Message-ID: <53088D04.2030509@grothoff.org> (raw)
In-Reply-To: <530863FE.4080107@totakura.in>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
On 02/22/2014 09:46 AM, Sree Harsha Totakura wrote:
> This is likely to cause the load on the system. 'gnunet-service-nse'
> tries to find a proof-of-work to participate in the size estimation
> application of GNUnet. This proof-of-work involves find a value whose
> hash matches its first n digits; this is required to avoid Sybil attacks
> and can be computationally expensive and can be taxing on the loongson
> you have.
>
> I am not sure if the NSE service is needed for this testcase. If not it
> should be easy to fix.
I've disabled the POW calculation in SVN 32456, so the CPU load issue
should be fixed now.
[-- Attachment #2: 0x48426C7E.asc --]
[-- Type: application/pgp-keys, Size: 7098 bytes --]
prev parent reply other threads:[~2014-02-22 11:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 6:22 GNUnet build failure on mips64el Mark H Weaver
2014-02-21 11:27 ` Andreas Enge
2014-02-21 13:01 ` Sree Harsha Totakura
2014-02-21 15:31 ` Ludovic Courtès
2014-02-21 15:39 ` Andreas Enge
2014-02-21 17:49 ` Ludovic Courtès
2014-02-21 18:20 ` Andreas Enge
2014-02-25 9:05 ` Andreas Enge
2014-02-27 21:29 ` Build timeout on Hydra Ludovic Courtès
2014-02-21 23:33 ` GNUnet build failure on mips64el Sree Harsha Totakura
2014-02-21 12:54 ` Sree Harsha Totakura
2014-02-21 21:46 ` Mark H Weaver
2014-02-21 23:28 ` Sree Harsha Totakura
2014-02-22 7:44 ` Mark H Weaver
2014-02-22 8:46 ` Sree Harsha Totakura
2014-02-22 11:41 ` Christian Grothoff [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53088D04.2030509@grothoff.org \
--to=christian@grothoff.org \
--cc=guix-devel@gnu.org \
--cc=sreeharsha@totakura.in \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).