304721 – Use 'size of downloads' as additional parallel-fetch package ordering key

Bug 304721 - Use 'size of downloads' as additional parallel-fetch package ordering key

Summary: Use 'size of downloads' as additional parallel-fetch package ordering key

Status:	RESOLVED DUPLICATE of bug 257073

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Core - Dependencies (show other bugs)
Hardware:	All Linux

Importance:	High enhancement
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2010-02-12 11:25 UTC by Michał Górny
Modified:	2010-02-17 04:04 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michał Górny archtester

2010-02-12 11:25:52 UTC

Portage could use 'size of downloads' (i.e. amount of additional data that needs to be downloaded before building the package) whenever sorting sibling nodes in the dependency tree.

For example, with current ordering it is possible that www-client/chromium (140M of download) will be placed before much smaller, totally unrelated packages. In this case, non-parallel build process will be stalled for a few minutes required to download the package and start building it.

With download-size ordering, portage would place unrelated, smaller packages before chromium so that less time would be wasted waiting for download to complete (with parallel-fetch enabled).

Comment 1 Zac Medico gentoo-dev

2010-02-17 04:04:31 UTC


*** This bug has been marked as a duplicate of bug 257073 ***