Per tab CPU usage
Moderator: trava90
Forum rules
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
This board is for technical/general usage questions and troubleshooting for the Pale Moon browser only.
Technical issues and questions not related to the Pale Moon browser should be posted in other boards!
Please keep off-topic and general discussion out of this board, thank you!
-
- Pale Moon guru
- Posts: 35638
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Per tab CPU usage
Search is your friend.
Short answer: no.
Short answer: no.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Per tab CPU usage
The problem: some open tabs and palemoon process is the cpu hog.
However its not palemoon but likely some ill javascript in one of the tabs stealing the cpu resources.
Is it possible to stop javascript by tab?
However its not palemoon but likely some ill javascript in one of the tabs stealing the cpu resources.
Is it possible to stop javascript by tab?
-
- Moon Magic practitioner
- Posts: 2194
- Joined: 2018-05-05, 13:29
Re: Per tab CPU usage
Try something like uMatrix.kilroi wrote:The problem: some open tabs and palemoon process is the cpu hog.
However its not palemoon but likely some ill javascript in one of the tabs stealing the cpu resources.
Is it possible to stop javascript by tab?
Search the forum for instructions on installing the last compatible version.
Re: Per tab CPU usage
Thank you, I was also looking for such soft for other reasons. Well I have nothing to hide, but ...
Re: Per tab CPU usage
And withMoonchild wrote:Search is your friend.
Short answer: no.
Code: Select all
about:performance
There are some cpu % usage there.
-
- Pale Moon guru
- Posts: 35638
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Per tab CPU usage
Keep the age of my response in mind.
Before August 2018, we were on Tycho, where about:performance didn't exist.
On UXP, we indeed have about:performance, but please understand that that page is a hell of a lot of guesswork, not in the least because certain resources are shared between tabs. Its usability is limited but it can be used as an aid to guess which page or extension is being too CPU/resource hungry. Never more than an educated guess, though.
Before August 2018, we were on Tycho, where about:performance didn't exist.
On UXP, we indeed have about:performance, but please understand that that page is a hell of a lot of guesswork, not in the least because certain resources are shared between tabs. Its usability is limited but it can be used as an aid to guess which page or extension is being too CPU/resource hungry. Never more than an educated guess, though.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Per tab CPU usage
You're right, my mistake, didn't see post date.Moonchild wrote:Keep the age of my response in mind.
Before August 2018, we were on Tycho, where about:performance didn't exist.
-
- Fanatic
- Posts: 122
- Joined: 2017-06-21, 02:37
Re: Per tab CPU usage
Shouldn't it be removed? Not only because it's imprecise but its related components add "non-trivial" overhead to the JavaScript engine. Related Bugzilla entries are 1309946, 1406872 and 1498195Moonchild wrote:Keep the age of my response in mind.
Before August 2018, we were on Tycho, where about:performance didn't exist.
On UXP, we indeed have about:performance, but please understand that that page is a hell of a lot of guesswork, not in the least because certain resources are shared between tabs. Its usability is limited but it can be used as an aid to guess which page or extension is being too CPU/resource hungry. Never more than an educated guess, though.
Re: Per tab CPU usage
Is it adding overhead when not loaded? As for should it be removed? Likely but maybe not.. I think while it is loaded the overhead of its self may make it less useful. So I dunno.
-
- Fanatic
- Posts: 122
- Joined: 2017-06-21, 02:37
Re: Per tab CPU usage
It sounds like it.New Tobin Paradigm wrote:Is it adding overhead when not loaded? As for should it be removed? Likely but maybe not.. I think while it is loaded the overhead of its self may make it less useful. So I dunno.
-
- Pale Moon guru
- Posts: 35638
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Per tab CPU usage
Actually, the overhead is called non-trivial but that is just best guess. It's a simple stopwatch and that doesn't take much in terms of processing.
Some relevant quotes from the people who designed this:
Some relevant quotes from the people who designed this:
<Yoric> It should not take any visible time when about:performance is closed.
When its performance impact was questioned::Yoric wrote:the main reason for which I had to come up with the Stopwatch, rather than reusing the profiler API, was that, after having discussed it with BenWa, we concluded that the profiler API was too heavy-handed/expensive for the task. I do not remember the exact criteria, but the profiler API wakes up the entire process once per ms (even if the process is paged out, if my memory serves), which is pretty bad, battery-wise and possibly CPU-wise. Also, I seem to remember that it uses lots of memory.
So I'm pretty confident the overhead this adds is minimal and won't have any real-world impact.:Yoric wrote:Before I landed this code, ~18 months ago, I spent several days profiling it on every site that I could think of (I'm almost sure that GSuite was included) and AutoStopwatch didn't show up. Nor did it show up on Talos, Arewefastyet, etc.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
Re: Per tab CPU usage
The real question is.. Is any of this useful to anyone? Or rather, is it useful enough to anyone to keep?
-
- Pale Moon guru
- Posts: 35638
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Per tab CPU usage
The fact this thread exists is an indicator that at least some people find it useful...
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
- Moon Magic practitioner
- Posts: 2194
- Joined: 2018-05-05, 13:29
Re: Per tab CPU usage
You could also try placing some giant header in about:performance saying something along the lines of "this feature is deprecated and will be removed in a future version", without touching anything else.
If someone complains you "undeprecate" it (basically just remove the header), otherwise, if no one says anything in a year or two (or twenty, paraphrasing a certain famous software), you remove the stopwatch.
Of course assuming you decide to remove it in the first place.
If someone complains you "undeprecate" it (basically just remove the header), otherwise, if no one says anything in a year or two (or twenty, paraphrasing a certain famous software), you remove the stopwatch.
Of course assuming you decide to remove it in the first place.
-
- Pale Moon guru
- Posts: 35638
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Per tab CPU usage
I'm pretty confident the overhead this adds is minimal and won't have any real-world impact.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
-
- Pale Moon guru
- Posts: 35638
- Joined: 2011-08-28, 17:27
- Location: Motala, SE
Re: Per tab CPU usage
If people think it needs some actual measurements, I can add a preference to control this performance measuring code, so people can test the difference with it on or off. Tit for tat, though, if I put time into adding the pref, I do expect people to follow-up with actual quantifiable measuring experiments to see if there is a significant overhead or not.
"Sometimes, the best way to get what you want is to be a good person." -- Louis Rossmann
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite
"Seek wisdom, not knowledge. Knowledge is of the past; wisdom is of the future." -- Native American proverb
"Linux makes everything difficult." -- Lyceus Anubite