Hi all!
I'm (again) in the process of optimizing my laptops power consumption. I noticed that "tdepowersafe" consumes ~ 2.5% of all CPU cycles - this is more than Xorg (1.6%) but less than htop (6.3%). So my question is: does tdepowersafe do constant polling? IMO it should take almost no CPU cycles (<1%)?
Nik
-- Please do not email me anything that you are not comfortable also sharing with the NSA, CIA ...
07.10.24 17:34, Dr. Nikolaus Klepp via tde-devels:
I'm (again) in the process of optimizing my laptops power consumption. I noticed that "tdepowersafe" consumes ~ 2.5% of all CPU cycles - this is more than Xorg (1.6%) but less than htop (6.3%). So my question is: does tdepowersafe do constant polling? IMO it should take almost no CPU cycles (<1%)?
That is mostly through tdehw which in some cases can to freeze interfaces and so I have fixed the issue for myself in the patch tdehw-NoFreeze.patch https://bugs.pearsoncomputing.net/show_bug.cgi?id=3199, also as many other TDE issues like this one. :)
So, I have not more than 0.5% CPU loading on 800 МГЦ CPU by tdepowersafe!
Regards, Roman
Anno domini 2024 Wed, 9 Oct 19:40:53 +0300 Roman Savochenko via tde-devels scripsit:
07.10.24 17:34, Dr. Nikolaus Klepp via tde-devels:
I'm (again) in the process of optimizing my laptops power consumption. I noticed that "tdepowersafe" consumes ~ 2.5% of all CPU cycles - this is more than Xorg (1.6%) but less than htop (6.3%). So my question is: does tdepowersafe do constant polling? IMO it should take almost no CPU cycles (<1%)?
That is mostly through tdehw which in some cases can to freeze interfaces and so I have fixed the issue for myself in the patch tdehw-NoFreeze.patch https://bugs.pearsoncomputing.net/show_bug.cgi?id=3199, also as many other TDE issues like this one. :)
So, I have not more than 0.5% CPU loading on 800 МГЦ CPU by tdepowersafe!
Regards, Roman
That's perfect. Is this patch going to be integrated ay time soon?
Nik
09.10.24 20:04, Dr. Nikolaus Klepp via tde-devels:
Anno domini 2024 Wed, 9 Oct 19:40:53 +0300 Roman Savochenko via tde-devels scripsit:
07.10.24 17:34, Dr. Nikolaus Klepp via tde-devels:
I'm (again) in the process of optimizing my laptops power consumption. I noticed that "tdepowersafe" consumes ~ 2.5% of all CPU cycles - this is more than Xorg (1.6%) but less than htop (6.3%). So my question is: does tdepowersafe do constant polling? IMO it should take almost no CPU cycles (<1%)?
That is mostly through tdehw which in some cases can to freeze interfaces and so I have fixed the issue for myself in the patch tdehw-NoFreeze.patch https://bugs.pearsoncomputing.net/show_bug.cgi?id=3199, also as many other TDE issues like this one. :)
So, I have not more than 0.5% CPU loading on 800 МГЦ CPU by tdepowersafe!
Regards, Roman
That's perfect. Is this patch going to be integrated ay time soon?
This one and more other patches integrated in my different repositories with regularly updated LiveDisks — http://oscada.org/wiki/Sub-projects/Automation_Linux_distributive
To the main branch of TDE their just aren't merged by the local "authorities". :)
Roman Savochenko via tde-devels wrote:
And there is no need in chances, you just load a LiveDisk and test-ascertain! :)
well here tdepowersave runs at 0.1% ... I actually downloaded some years ago to have a look, but I am doing my own Frankenstein ... with least customizations possible - would be rather extentions on top (only when needed). Over the years I found out that it is better in this case to swim with one swarm that suits 99% of the needs. It saves a lot of time. I don't even do kernel compilation myself anymore. It might be result of inflation in available time over the years :).
10.10.24 02:22, deloptes via tde-devels:
Roman Savochenko via tde-devels wrote:
And there is no need in chances, you just load a LiveDisk and test-ascertain! :)
well here tdepowersave runs at 0.1% ...
OK
I actually downloaded some years ago to have a look, but I am doing my own Frankenstein ... with least customizations possible - would be rather extentions on top (only when needed). Over the years I found out that it is better in this case to swim with one swarm that suits 99% of the needs. It saves a lot of time.
For that I have created a script of migration my specific-work configuration during updating to new distributive version.
That is, I install new version from such LiveDisk in other partition, next just call this script, and bingo — use the familiar ready environment mostly without extra actions.
I don't even do kernel compilation myself anymore. It might be result of inflation in available time over the years :).
I don't build kernels 14 years already and for such LiveDisks I built a kernel yet for ALTLinux 6.0 just to its work on K6-2.
And next stopped (or started) on Debian 7 with 486 kernels here from the box, and it works right now on my nearly first PC K6-2+/570, which installed from such actual LiveDisk, and which (TDE14.0.10) I newly even fixed about udisks, playing DVD in Kaffeine and CD-RW icons. :)