From: Igor <lanthruster@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Portage QOS
Date: Fri, 10 Jan 2014 16:23:10 +0400 [thread overview]
Message-ID: <52cfe62f.6104980a.5664.388e@mx.google.com> (raw)
In-Reply-To: <86r48g8zdc.fsf@moguhome00.in.awa.tohoku.ac.jp>
Hello Heroxbd,
Friday, January 10, 2014, 4:16:47 AM, you wrote:
>> The ebuilds have approximately the same time to install, the failure
>> rate is about the same, emerge is getting slower.
> I am curious about the slowness of emerge.
> How about profile the portage and rewrite the time-crucial part in
> C/C++, or ideally, borrowing the counterpart from paludis? How feasible
> is that?
> I guess the dep-tree calculation is the slowest part.
If you had the PortageQOS you would see what change slowed down
Portage. And the problem could have already been fixed.
You could make fast and correct decisions. True, it could be possible
that some parts of the portage need to be rewritten. May be Python was
the wrong decision, may be it's better to use C++.
(Yes, I expect to be
condemned over here before I'm banned, a sacrifice for the better Gentoo
somebody had to make).
Do you remember how many problems portage had with Python? It's like
Gentoo is for Python not for anything else.
Why not to get rid of Python at all. What is so great in Python that
Gentoo exists for the sake of it?
And when next thing is introduced - you can see how it works
world wide.
On some older PC the new portage works for 4-6 minutes before it FAILS.
If the portage is going to be a little bit smarter again - you would need a
new hardware to run it.
And nobody cares, of course it's better to hide don't know or run from
problems than know about them and fix them.
300 devs, are NOT ABLE to make portage fast in 8 years.
--
Best regards,
Igor mailto:lanthruster@gmail.com
next prev parent reply other threads:[~2014-01-10 12:23 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 [this message]
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
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=52cfe62f.6104980a.5664.388e@mx.google.com \
--to=lanthruster@gmail.com \
--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