unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Server unrresponsive
Date: Fri, 30 Jan 2015 10:20:48 +0100	[thread overview]
Message-ID: <20150130092047.GA3770@intra> (raw)
In-Reply-To: <87r3ufri07.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

I kindof presumed it was the bandwidth to hydra which was the problem.  Not the 
machine itself.

Are you sure which problem needs to be solved before we spend $$$ on it?

On Tue, Jan 27, 2015 at 11:11:36PM +0100, Ludovic Courtès wrote:
     
     I think we have just the right size in terms of x86 build machines.  The
     front-end itself shouldn’t also be a build machine, because it already
     has enough to do (evaluations + HTTP requests, which includes providing
     compressed archives on demand.)
     
     So I would like to keep hydra.gnunet.org as a build machine and to
     switch to a dedicated box for the front-end.
     
     The FSF might be able to help with that, otherwise we’ll go ahead and
     get ourselves another machine, I think.  But I think it’s time to fix
     that issue now.
     
     Thanks,
     Ludo’.
     

-- 
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2015-01-30  9:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20 23:18 Server unrresponsive Daniel Pimentel
2015-01-21 15:04 ` Ludovic Courtès
2015-01-21 15:08   ` Daniel Pimentel
2015-01-27 21:54   ` Sree Harsha Totakura
2015-01-27 22:11     ` Ludovic Courtès
2015-01-30  9:20       ` John Darrington [this message]
2015-01-30 15:04         ` Adam Pribyl
2015-02-01 19:08           ` Ludovic Courtès

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=20150130092047.GA3770@intra \
    --to=john@darrington.wattle.id.au \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    /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).