All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: bitbake-devel <bitbake-devel@lists.openembedded.org>,
	Joshua Watt <JPEWhacker@gmail.com>,
	Michael Halstead <mhalstead@linuxfoundation.org>
Subject: Re: [bitbake-devel] hashserv performance issues
Date: Wed, 22 May 2024 14:17:02 +0100	[thread overview]
Message-ID: <f13fdebcfa74757dbc51a79da995f47238873be7.camel@linuxfoundation.org> (raw)
In-Reply-To: <17D1D17091A0A935.11581@lists.openembedded.org>

Joshua reminded me of how to get the server stats (thanks).

For our public server:

$ bitbake-hashclient --address wss://hashserv.yoctoproject.org/ws stats
{
    "requests": {
        "average": 0.06250257539454776,
        "max_time": 16.712204183917493,
        "num": 381569673,
        "stdev": 0.18345958610620752,
        "total_time": 23849087.254955433
    }
}

Compared to my local system:

$ bitbake-hashclient --address ws://localhost:8686 stats
{
    "requests": {
        "average": 0.0004462178160857849,
        "max_time": 0.04537125899992134,
        "num": 3121,
        "stdev": 0.00163338261679226,
        "total_time": 1.3926458040037346
    }
}

For a world build with 38000 tasks, 38000 * 0.0625 = 2375 seconds or 39
minutes, so I suspect the hash server performance is a real issue here
:(

Michael: Is there anything we can do?

Cheers,

Richard


       reply	other threads:[~2024-05-22 13:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <17D1D17091A0A935.11581@lists.openembedded.org>
2024-05-22 13:17 ` Richard Purdie [this message]
2024-05-23 10:11   ` [bitbake-devel] hashserv performance issues Jan-Simon Möller
2024-05-23 10:45     ` Richard Purdie

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=f13fdebcfa74757dbc51a79da995f47238873be7.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=JPEWhacker@gmail.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=mhalstead@linuxfoundation.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.