public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Current 'next' won't build
Date: Mon, 23 Oct 2017 15:22:27 +0100	[thread overview]
Message-ID: <1508768547.4838.45.camel@ipfire.org> (raw)
In-Reply-To: <08de7769-3823-37a0-da15-b0b01b475d09@ipfire.org>

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

Hi,

did you test if this is a hard limit for all threads together? 

If so that would be quite nice because we can use -9 then and it would just go
up to the ceiling of memory usage and then just cap the size of the dictionary
there (that's what I get from the man page).

I think we can even go up to 1GB since that is a minimum each build system
should have. I would really like to see that extra 10-15MB shaven off the ISO
image.

Would you like to send a patch with all of this? I reverted all previous commits
again because the nightly builds failed.

Best,
-Michael

On Thu, 2017-10-19 at 21:10 +0200, Matthias Fischer wrote:
> Hi,
> 
> On 18.10.2017 19:42, Michael Tremer wrote:
> > Did you compare image size after? Is that being influenced by the memory
> > parameter?
> 
> For the records:
> 
> Current 'next', as in previous posting:
> 
> Buildtime 03:59:03
> 
> ***SNIP***
> -rw-r--r--   1 root root 255029305 Oct 19 05:15 ipfire-2.19.1gb-ext4.i586-
> full-core115.img.gz
> -rw-r--r--   1 root root        80 Oct 19 05:26 ipfire-2.19.1gb-ext4.i586-
> full-core115.img.gz.md5
> -rw-r--r--   1 root root 252170425 Oct 19 05:19 ipfire-2.19.1gb-ext4-
> scon.i586-full-core115.img.gz
> -rw-r--r--   1 root root        85 Oct 19 05:26 ipfire-2.19.1gb-ext4-
> scon.i586-full-core115.img.gz.md5
> -rw-r--r--   1 root root 184549376 Oct 19 04:50 ipfire-2.19.i586-full-
> core115.iso
> -rw-r--r--   1 root root        68 Oct 19 05:26 ipfire-2.19.i586-full-
> core115.iso.md5
> -rw-r--r--   1 root root      3522 Oct 19 05:26 ipfire-2.19.xen.i586-
> downloader-core115.tar.bz2
> -rw-r--r--   1 root root        82 Oct 19 05:26 ipfire-2.19.xen.i586-
> downloader-core115.tar.bz2.md5
> ***SNAP***
> 
> 'xz' updated to '5.2.3', "optimized":
> 
> Build time 3:30:05
> ***SNIP***-rw-r--r--   1 root root 255172283 Oct 19 20:41 ipfire-2.19.1gb-
> ext4.i586-full-core115.img.gz
> -rw-r--r--   1 root root        80 Oct 19 20:54 ipfire-2.19.1gb-ext4.i586-
> full-core115.img.gz.md5
> -rw-r--r--   1 root root 252156393 Oct 19 20:45 ipfire-2.19.1gb-ext4-
> scon.i586-full-core115.img.gz
> -rw-r--r--   1 root root        85 Oct 19 20:54 ipfire-2.19.1gb-ext4-
> scon.i586-full-core115.img.gz.md5
> -rw-r--r--   1 root root 175112192 Oct 19 20:14 ipfire-2.19.i586-full-
> core115.iso
> -rw-r--r--   1 root root        68 Oct 19 20:54 ipfire-2.19.i586-full-
> core115.iso.md5
> -rw-r--r--   1 root root      3531 Oct 19 20:54 ipfire-2.19.xen.i586-
> downloader-core115.tar.bz2
> -rw-r--r--   1 root root        82 Oct 19 20:54 ipfire-2.19.xen.i586-
> downloader-core115.tar.bz2.md5
> ***SNAP***
> 
> Looks interesting?
> 
> Best,
> Matthias

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-10-23 14:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-18  2:39 Matthias Fischer
2017-10-18  2:39 ` Michael Tremer
2017-10-18 13:56   ` Matthias Fischer
2017-10-18 14:22     ` Matthias Fischer
2017-10-18 14:50       ` Michael Tremer
2017-10-18 15:54         ` Matthias Fischer
2017-10-18 17:03           ` Matthias Fischer
2017-10-18 17:42             ` Michael Tremer
2017-10-19 14:00               ` Matthias Fischer
2017-10-19 19:10               ` Matthias Fischer
2017-10-23 14:22                 ` Michael Tremer [this message]
2018-04-29 11:53 Matthias Fischer
2018-04-29 12:08 ` Peter Müller
2018-12-23  9:59 Matthias Fischer
2018-12-25  8:22 ` Michael Tremer
2019-06-08 10:20 Matthias Fischer
2019-06-08 10:21 ` Michael Tremer
2019-06-08 10:33   ` Matthias Fischer
2019-06-08 10:35     ` Michael Tremer
2019-06-08 11:38       ` Matthias Fischer

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=1508768547.4838.45.camel@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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