From 1be510f9529cb082f802408b472a77d074b394c0 Mon Sep 17 00:00:00 2001 From: Nicolas Vigier Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- zarb-ml/mageia-sysadm/2011-April/003323.html | 82 ++++++++++++++++++++++++++++ 1 file changed, 82 insertions(+) create mode 100644 zarb-ml/mageia-sysadm/2011-April/003323.html (limited to 'zarb-ml/mageia-sysadm/2011-April/003323.html') diff --git a/zarb-ml/mageia-sysadm/2011-April/003323.html b/zarb-ml/mageia-sysadm/2011-April/003323.html new file mode 100644 index 000000000..3e18e4d81 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-April/003323.html @@ -0,0 +1,82 @@ + + + + [Mageia-sysadm] multiple builds on each nodes + + + + + + + + + +

[Mageia-sysadm] multiple builds on each nodes

+ Pascal Terjan + pterjan at gmail.com +
+ Sat Apr 9 17:00:41 CEST 2011 +

+
+ +
On Sat, Apr 9, 2011 at 15:55, nicolas vigier <boklm at mars-attacks.org> wrote:
+> Hello,
+>
+> ulri is now running two builds on each node at the same time.
+>
+> This improve a lot the average time to have a package built, when a big
+> package like libreoffice is in the queue.
+>
+> However I don't know what happens with many smaller packages in the
+> queue. To make sure it is still acceptable, we should do a benchmark.
+>
+> So I propose to make a list of 20 packages that we rebuild, with one
+> build on each node, and again with two builds on each node. And compare
+> the time it took to build all packages, in each case.
+>
+> I plan to do this tonight, when build of libreoffice is finished.
+
+Another case which I fear is the build of two huge packages (like
+kernel + kernel-tmb)
+
+ + + + + + + + + + +
+

+ +
+More information about the Mageia-sysadm +mailing list
+ -- cgit v1.2.1