public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Naohiro Aota <naota@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Portage QOS
Date: Sun, 12 Jan 2014 00:00:58 +0900	[thread overview]
Message-ID: <87mwj2h8b9.fsf@elisp.net> (raw)
In-Reply-To: <52ce4eab.463f700a.4b43.16bd@mx.google.com> (LTHR's message of "Thu, 9 Jan 2014 11:24:25 +0400")

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

Hi, Igor

LTHR <lanthruster@gmail.com> writes:

> Portage QOS
>
> Hi All,
>
> What do you think about implementing this:
>
> http://forums.gentoo.org/viewtopic.php?p=7477494
>
> I've system design in my head and could write it down with the
> implementation details.
> Then may be we could all review it and get to something we all agree
> upon then I could 
> try getting a team and implement it.
>
> Just a brief question - does anyone know how many ebuilds are
> assembled world 
> wide each second?

This is quite impressive for me. I'm one who have been thinking like
this. For the purpose, I started a Web service named GenTwoo on May
2011: http://gentwoo.elisp.net/?locale=en

First a GenTwoo user login with Twitter account to the service and
installs a tiny script [1] on their Gentoo box. Then each time they run
emerge, the script collect what package is emerged, if the emerge is
succeed or failed, its elog output, and its build.log (only if the
emerge failed). These information is sent to my server and tweeted
periodically with "#gentwoo" hash tag so that you can see your friends are
heating their computer :-). [2] 

You can also browse:

- What all GenTwoo users emerge recently
  http://gentwoo.elisp.net/emerges?locale=en
- What one user emerge recently
  http://gentwoo.elisp.net/users/naota344?locale=en
- How a emerge failed (click "error log" tab)
  http://gentwoo.elisp.net/emerges/644259?locale=en
- Recent popular packages
  http://gentwoo.elisp.net/poppackage?locale=en
- How long dose it take to emerge a package (and its average)
  http://gentwoo.elisp.net/packages/app-text/poppler/?locale=en#0.24.5

Since I'm not much advertising the project, there are not so many active
users (and they are mostly Japanese): there are only 54 users who ever
emerged since Dec 2013. I'm not sure my GenTwoo project completely suit
your demand, but there are already many emerge record on my server
(645112 emerge records since the service started, and 22129 emerges
since Dec 2013). So if you are interested, you can start "PortStat" or
"PortStatDEV" implementation immediately with the emerge data I have. Or
you can also join GenTwoo if you feel it's better to start from
scratch. I'd appreciate it if you would join GenTwoo project and improve
it together ;-) There's also on going project to rewrite GenTwoo into a
package stat [3]

Anyway, feel free to ask me GenTwoo's implementation detail if you are
interested in it. I think I can help you write your design idea if you
start from scratch with your idea.

[1] https://github.com/naota/gentwoo/blob/master/client/gentwoo.py
[2] https://twitter.com/search?q=%23gentwoo&f=realtime
[3] https://github.com/gentoo/GenTwoo-backend/

Regards,

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

  parent reply	other threads:[~2014-01-11 15:01 UTC|newest]

Thread overview: 57+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-09  7:24 [gentoo-dev] Portage QOS LTHR
2014-01-09  8:12 ` Alec Warner
2014-01-09 12:44   ` Igor
2014-01-09 14:12     ` Christopher Schwan
2014-01-09 15:26       ` Igor
2014-01-09 15:55         ` Jeroen Roovers
2014-01-09 16:37           ` Igor
2014-01-10  0:27             ` heroxbd
2014-01-10 12:41               ` Igor
2014-01-10 13:51                 ` Rich Freeman
2014-01-10  0:16         ` heroxbd
2014-01-10  0:31           ` Patrick Lauer
2014-01-10  1:19             ` Tom Wijsman
2014-01-10  1:52               ` Patrick McLean
2014-01-10  2:40                 ` Tom Wijsman
2014-01-10  6:17                 ` Brian Dolbec
2014-01-10 18:14                 ` Ciaran McCreesh
2014-01-10  7:54             ` heroxbd
2014-01-10 18:11             ` Ciaran McCreesh
2014-01-11  3:57               ` Patrick Lauer
2014-01-10  1:02           ` Tom Wijsman
2014-01-10  9:10             ` heroxbd
2014-01-10 14:54               ` Tom Wijsman
2014-01-10 12:23           ` Igor
2014-01-10 12:30             ` René Neumann
2014-01-10 12:30           ` Igor
2014-01-10 12:39             ` Patrick Lauer
2014-01-10 13:05               ` Igor
2014-01-10 13:18                 ` René Neumann
2014-01-10 18:19                   ` Ciaran McCreesh
2014-01-10 19:06                     ` René Neumann
2014-01-10 14:05                 ` heroxbd
2014-01-12 10:47                 ` [gentoo-dev] " Steven J. Long
2014-01-10 13:10               ` [gentoo-dev] " Igor
2014-01-10 14:02                 ` Rich Freeman
2014-01-10 15:16                   ` Tom Wijsman
2014-01-10 18:12           ` Ciaran McCreesh
2014-01-09 15:49     ` Ben Kohler
2014-01-09 16:11       ` Igor
2014-01-09 17:59     ` [gentoo-dev] " Duncan
2014-01-09 20:42       ` Igor
2014-01-09 21:08         ` Chris Reffett
2014-01-10 12:10           ` Igor
2014-01-10 12:26             ` René Neumann
2014-01-10 12:52               ` Igor
2014-01-10 12:57                 ` René Neumann
2014-01-10 15:39                 ` Tom Wijsman
2014-01-10 16:36             ` Mike Frysinger
2014-01-10 18:17             ` Greg KH
2014-01-10 19:38           ` Duncan
2014-01-10 22:36             ` heroxbd
2014-01-11  1:28               ` Duncan
2014-01-09 19:35 ` [gentoo-dev] " yac
2014-01-11 15:00 ` Naohiro Aota [this message]
2014-01-12 10:28   ` Igor
2014-01-12 19:31   ` Igor
2014-01-12 19:31   ` Igor

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=87mwj2h8b9.fsf@elisp.net \
    --to=naota@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox