Received: from out0.migadu.com (out0.migadu.com [94.23.1.103]) by nld3-dev1.alpinelinux.org (Postfix) with ESMTPS id 76495780DB4 for ; Mon, 12 Sep 2022 10:12:23 +0000 (UTC) MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ayaya.dev; s=key1; t=1662977541; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=4JZ7JTooOXAN6yQK4NPsaNwa2anFwVCS3LJiLSusPhA=; b=s1K2jaABrzozJG9PqsXjMsbo4J7wnk/a++q2MFHpEoY5hw58XwIjiItyyh8miWM09KhAFP XWKWRxh9ahgLUl4/rElOMmsGlI2QgEol92RKlzWynaiJY/OIAnpAZ9OYItv2L7k6ijOKlV AuhYLnk1ID6c5xrBgvpznZd9Gu0a87s= Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Mon, 12 Sep 2022 12:12:20 +0200 Message-Id: Subject: Re: performance drop with alpine linux upgrade X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "alice" To: "Riccardo Mottola" , "alpine-user" References: <196e1b55-ade9-8a4b-889b-006fef7f63c1@libero.it> In-Reply-To: <196e1b55-ade9-8a4b-889b-006fef7f63c1@libero.it> X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: ayaya.dev On Mon Sep 12, 2022 at 10:47 AM CEST, Riccardo Mottola wrote: > Hello, > > I upgraded Alpine Linux to 3.16 on my old Celeron-based Laptop. > > now, the same task of compiling the Arctic Fox browser takes instead of > about 4 hours, almost 10 days!! I extra left it running until I get the > same compile error as before. > It is a bit extreme performance drop! > I noticed that while compiling, the laptop fan does not ran constantly > at high speed, but it remains quited for a period, then spins up, then > quiet again, even if CPU is 100%. you should monitor the frequency during that- it probably goes down/up as the fans do > > I can think of two causes, from my past experience with other systems: > - disabled caches i don't think a kernel update would change this, either > - CPU not runnig at full speed > > In the BIOS I checked and CPU and L2 caches are enabled (small in this > crippled CPU anyway). > Could some APM/ACPI lower the cpu speed until I rise it withsome governor= ? you can check the governors with: cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor but i don't think even being stuck on "powersave" or something would do that.. strange you can change them to performance, which is usually the highest. the sane default is "schedutil" when the cpufreq driver supports it to balance power saving with performance, on some intel drivers the performance one is basically that. i don't think anything changed in the kernel defaults to make it powersave, so i'm not sure why it would be that bad. this sounds like some weird kernel regression in 5.15, if anything > > processor=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 0 > vendor_id=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : GenuineIntel > cpu family=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 15 > model=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 2 > model name=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : Mobile Intel(R) Celeron(R) CPU= 2.20GHz > stepping=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 9 > microcode=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 0x10 > cpu MHz=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 2194.366 > cache size=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 256 KB > physical id=C2=A0=C2=A0=C2=A0=C2=A0 : 0 > siblings=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 1 > core id=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 0 > cpu cores=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 1 > apicid=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 0 > initial apicid=C2=A0 : 0 > fdiv_bug=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : no > f00f_bug=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : no > coma_bug=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : no > fpu=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0 : yes > fpu_exception=C2=A0=C2=A0 : yes > cpuid level=C2=A0=C2=A0=C2=A0=C2=A0 : 2 > wp=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0 : yes > flags=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : fpu v= me de pse tsc msr pae mce cx8 sep mtrr pge mca > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts > cpuid cid xtpr > bugs=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : = cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass > l1tf mds swapgs itlb_multihit > bogomips=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 : 4390.59 > clflush size=C2=A0=C2=A0=C2=A0 : 64 > cache_alignment : 128 > address sizes=C2=A0=C2=A0 : 36 bits physical, 32 bits virtual > power management: > > Could some of the bug mitigation have such a strong impact? How can I > disable them in alpine? I don't think they would be a safety concern for > the kind of usage I have. add mitigations=3Doff to the kernel cmdline, via whatever booting setup you have. usual warnings/caveats apply, but there you go. i doubt they would be that impactful though.. > > Riccardo