**** BEGIN LOGGING AT Thu Feb 07 02:59:57 2019
Feb 07 06:42:26 <elvispre|cloud> Morning!
Feb 07 08:06:54 <Tofe> Morning!
Feb 07 08:24:57 <Herrie|Laptop> Morning!
Feb 07 08:37:10 <elvispre|cloud> Herrie|Laptop: A build optimisation I found is to prioritise the download of crucial build tools.
Feb 07 08:38:30 <elvispre|cloud> It saves me ~15 minutes to do something like...
Feb 07 08:39:55 <elvispre|cloud> bb gcc-sources binutils glibc    linux-libc-headers -c fetch && bb luneos-package
Feb 07 08:41:05 <elvispre|cloud> That would probably make less difference for you, but it might make a bit.
Feb 07 08:42:35 <JaMa> elvispre|cloud: looks strange, are you using a lot of bb threads with this?
Feb 07 08:43:00 <JaMa> because with sane number of bb threads the sheduler should do almost the same by default
Feb 07 08:43:50 <elvispre|cloud> JaMa: I have been doing a lot of experiments.
Feb 07 08:44:10 <JaMa> I mean with e.g. 8 bb threads it won't have much else to do until e.g. gcc-cross-* is finished building
Feb 07 08:44:40 <JaMa> but with e.g. 64 bb threads it will fetch a lot of stuff from the beginning, even when it's actually needed only much later
Feb 07 08:44:42 <elvispre|cloud> What happens is, these downloads start at a good time, but have to fight for bandwidth with lots of less important ones.
Feb 07 08:45:12 <JaMa> that's sign of too many bb threads for me
Feb 07 08:45:30 <elvispre|cloud> By your recommendation, yes I am using an insane number of BB threads :)
Feb 07 08:45:52 <JaMa> ok
Feb 07 08:46:08 <JaMa> I'm happy with 2-8 bb threads
Feb 07 08:46:10 <elvispre|cloud> I have a 24 thread processor and am using 48 BB threads.
Feb 07 08:47:35 <elvispre|cloud> 8 threads is a bit slower for me. 12 is also slower.
Feb 07 08:49:12 <elvispre|cloud> Mostly the full number of BB threads only gets used for CPU-lite tasks like fetching and populating sysroot.
Feb 07 08:50:12 <elvispre|cloud> (I am just enjoying myself trying to get even close to what Herrie can do :-) )
Feb 07 08:50:23 <JaMa> how big are load (cpu/mem) peaks with this?
Feb 07 08:53:03 <elvispre|cloud> I am not sure about that. I have 48 GB RAM and see no problems. The CPU gets maxed out on occasions but. The highest temperature I've seen is only  44 C.
Feb 07 08:54:09 <elvispre|cloud> I could monitor CPU/mem with top perhaps in Linux?
Feb 07 08:56:21 <elvispre|cloud> The WebOS ose build uses 48 threads on my CPU by default (was my reason for picking that number).
Feb 07 10:22:32 <Tofe> 44°C... <--- Herrie|Laptop did you see this ? :p
Feb 07 10:23:10 <Herrie|Laptop> Tofe: Well I'm not sure if my sensor software in Linux reports the correct temps... There was an issue where it would report 27c too high which was fixed in some kernel
Feb 07 10:23:14 <Herrie|Laptop> Not sure if it's fixed in mine
Feb 07 10:23:22 <Herrie|Laptop> So could be it reports 27c too high, hard to tell
Feb 07 10:23:29 <Herrie|Laptop> I need to check in Windows
Feb 07 10:23:50 <Herrie|Laptop> From what I've read I shouldn't be getting 80+c with my cooler, even under full load
Feb 07 10:24:14 <Tofe> Herrie|Laptop: it also depends on which sensor you choose, of course
Feb 07 10:25:02 <Herrie|Laptop> Tofe: Well there was an issue in the driver that caused too high reports which was supposedly fixed in various kernel & software bits, however unsure if it's in my kernel
Feb 07 10:25:08 <Herrie|Laptop> It's fixed in 4.19, I'm on 4.14
Feb 07 10:25:17 <Herrie|Laptop> However they also talk about 'backported'
Feb 07 10:25:25 <Herrie|Laptop> So I can either upgrade to 4.19 kernel and it should be gone
Feb 07 10:25:29 <Herrie|Laptop> Or test in Windows :P
Feb 07 10:32:27 <Herrie|Laptop> Ah I'm on 4.15
Feb 07 10:35:16 <Herrie|Laptop> Seems I need this patch for hwmon: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git/commit/?h=hwmon-next&id=484a84f25ca7817c3662001316ba7d1e06b74ae2
Feb 07 10:38:36 <Herrie|Laptop> Tofe: Any recommendations as for kernel version? UKUU is offering me 4.19.1 to 4.19.20 and 4.20 to 4.20.7
Feb 07 10:38:41 <Herrie|Laptop> Just latest & greatest or.... ?
Feb 07 10:50:00 <Herrie|Laptop> Seems I need 4.19 for Threadripper 2990WX, 4.20 doesn't seem to fix anything specific
Feb 07 10:50:06 <Herrie|Laptop> At least not for my CPU
Feb 07 11:11:45 <Herrie|Laptop> Let's just try latest
Feb 07 11:11:58 <Herrie|Laptop> Did the dkms RAID driver for kernel, so hopefully that's fine
Feb 07 11:21:26 <Herrie|Laptop> And it's doesn't come up after a reboot...
Feb 07 11:21:32 <Herrie|Laptop> Need to investigate tonight again LOL
Feb 07 11:58:35 <Tofe> Herrie|Laptop: without any specific reason, just stick to the latest
Feb 07 13:19:20 <levone1> Sorry if off-topic - just a quick question, if I could...  I came here based on a 'Contact' info blurb on the website, but I see in the headline here that discussion should be focused on the specific topic at hand.  Is there  a more general channel for discussion about other things, or some other appropriate way to do that?
Feb 07 13:19:59 <Herrie|Laptop> levone1: You can discuss here no problem :)
Feb 07 13:23:16 <levone1_> Thanks Herrie.  I'm in the middle of some things atm, but I'll be in tune...
Feb 07 13:24:47 <Herrie|Laptop> OK :)
Feb 07 20:25:22 <elvispre|cloud> Nmon seems to be a pretty good performance monitoring tool for Linux.
Feb 07 22:20:54 <elvispre> Using it, the reason setting PARALLEL_MAKE does not speed qt builds up is that they *are* multithreaded already.
**** ENDING LOGGING AT Fri Feb 08 02:59:56 2019