Bug#755043: Initial import needs more than 14GB of RAM
Hi,
On Thu, 17 Jul 2014, Vincent Bernat wrote:
> It has been running for a several hours in "Processing Packages files of
> unstable repository".
Note that you can skip that part if you edit the unstable repository
to disable the "binary" field. Most of the current features only
require source packages and this highly non-optimised import of binary
package data can be skipped.
It's exactly the same reasoning that lead me to disable the parsing of
Packages files for all the other repositorie (see commit
76d49846239497b3d867d7ba4f9a6af8c1ec64bf). I kept unstable only because
it's better but if it really creates problems for too many people
maybe it's best to disable it from this fixture until we improve that
part... or only consider a single arch, possibly.
> Maybe that would be useful but if you didn't get bothered by that, my
> point was essentially that it is difficult to get started because of
> this for a first-time contributor. For development, some kind of limit
> or a set of small fake repositories would be useful. A pre-made sqlite3
> database dump too but it may be too cumbersome to update and don't allow
> to work on every parts.
I understand. I like the idea of a pre-made sqlite3 database dump. For the
update part, we could possibly rely on jenkins.debian.net to do it for
us... that would be doable since I would like to use jenkins.debian.net to
run unit tests on all supported platforms (python3 / python2.7) and to run
functional tests too if possible. But that's another story.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Discover the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/
Reply to: