From: Alex Kost <alezost@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: HTTPS for Hydra
Date: Sat, 19 Mar 2016 10:59:10 +0300 [thread overview]
Message-ID: <8760wi290x.fsf@gmail.com> (raw)
In-Reply-To: <87mvpvjxz7.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Fri, 18 Mar 2016 22:08:12 +0100")
Ludovic Courtès (2016-03-19 00:08 +0300) wrote:
> Alex Kost <alezost@gmail.com> skribis:
>
>> Roel Janssen (2016-03-18 00:53 +0300) wrote:
>>
>>> Ludovic Courtès writes:
>> [...]
>>>> Starting from a few hours ago, nginx at hydra.gnu.org times out after
>>>> ~10s instead of 60s. So when hydra.gnu.org is loaded, the /api requests
>>>> time out and we don’t get build status icons.
>>>
>>> Well, 10 seconds is a lot of time. Time for a faster API response from
>>> Hydra ;)
>>
>> Heh, I also suffer from the slowness, as it makes impossible to look at
>> some particular Hydra info using emacs interface (for example, by
>> pressing "B" in a "Guix Package List" buffer), as things like this:
>>
>> http://hydra.gnu.org/api/latestbuilds?nr=3&job=wget-1.17.1.x86_64-linux
>>
>> always time out :-(
>
> I’ve noticed that too, but what to do?
I was just complaining :-) I realize that Hydra is horribly overloaded,
so apparently nothing can be done with this.
> 10 seconds is already way more than what is acceptable from a UI
> viewpoint. Increasing the timeout may contribute to increasing the load
> on the machine, too.
Sure, I didn't mean to increase the timeout. I agree with Roel that 10
seconds is a lot of time. As I said I was just complaining, and
actually I didn't expect any reply on that message. Sorry for
bothering :-)
--
Alex
next prev parent reply other threads:[~2016-03-19 7:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 22:56 HTTPS for Hydra Roel Janssen
2016-02-04 23:24 ` Leo Famulari
2016-03-15 21:35 ` Ludovic Courtès
2016-03-15 21:47 ` Roel Janssen
2016-03-15 22:01 ` Ludovic Courtès
2016-03-15 22:07 ` Roel Janssen
2016-03-16 2:08 ` Pjotr Prins
2016-03-16 16:11 ` Roel Janssen
2016-03-17 21:42 ` Ludovic Courtès
2016-03-17 21:53 ` Roel Janssen
2016-03-18 8:27 ` Alex Kost
2016-03-18 21:08 ` Ludovic Courtès
2016-03-19 7:59 ` Alex Kost [this message]
2016-03-18 21:05 ` 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=8760wi290x.fsf@gmail.com \
--to=alezost@gmail.com \
--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).