Firefox is slow - does multiple profile affect performance?
Firefox is slow; so slow I have to use another browser, Brave, to get around this.
It is not about 'how many open tabs' or 'what extensions are doing'. I can have one profile open with one tab and still wish there would be a better response.
I have lots of profiles. I think the performance was better when I first started Firefox on this computer. I wonder If I eliminate profiles will I get a better performance.
How do I go proving this? - How easy can I take the profiles folder copy and rename it then start firefox with a profile folder and only one profile and one tab then What?
I did not gain a significant advantage in the load times for firefox. The load time for the browser with only the one empty tab 22 - 26 seconds . The load time for yahoo.com main page 31 -36 seconds. The load time for a link on the yahoo main page 20 - 22 seconds.
The question was "does having a large profile folder slow response time for firefox"? I believe I am seeing that this is true. When I load the yahoo profile it can take 10+ seconds more to resolve the main page and up to an addition 5-7 seconds to resolve the opened tabs.
Know that the browser was the only user process opened at the times of the tests. Know that the internet connection is the primier package and I have been monitoring the speeds frequently recently. I am good with the internet connection times. Know that I know the quick fixes and either there was no improvement or the inconvience of doing with out dark reader is no option.
Now understand I did not run these tests through a testing suite. These test were a couple one offs I used to form an opinion. Everyday usage forms an opinion in everyday users without hard data to coincide with the usage.
由 GIlbert Bigelow 於 修改
所有回覆 (3)
Firefox only loads one profile, and regardless of how many profiles you have, it should make no difference.
Start Firefox using Troubleshoot(Safe) Mode {web link}
A small dialog should appear. Click Start In Troubleshoot(Safe) Mode (not Refresh). Is the problem still there?
@FredMcD Thanks for the reply. Good suggestion you have.
The testing has two parts. In one part two tests commence as soon as the desktop icon is pressed.
One of these test is the response time it takes for the computer to present the browser frame.
The second test measures how long it takes after the browser frame is established until browser is fully loaded. Know this set of the test has two sub-test that are kind of tied together in that they start at the same time and try to measure the same performance metrics with two different mindset/ criteria.
There is a further connection between these two tests. One, I need the time it takes for the browser frame to be presented so I can take that time into consideration when evaluating the quality of the browsers different characteristics. The second of these two test is to measure the over all time, remove the time for the browser frame to present and weigh the remainder of that set/ test by two factors, the over all time/ total process power minus the over all time/ Firefox process power.
In consideration this is to know that a portion, though an undetermined portion, of that time to present the browser frame is used by the operating system as well as by the browser processes. It is expected that the computers' available resources to operate the browser will grow after the browser opening process have terminated. It is expected that the amount of operating system process power required to Firefox will diminish after initialization and therefore allow the most accurate assumption of this test and that is to see just how much of this slowness is attributed to Firefox and how much to the operating system. And, trying to conceive how to show how much of this is mismanaged resources.
The second test is to measure how much time a random tab will open in.
Your suggestion will help with the second test; but, the first, most painful part, the initialization. This is the one part of the Firefox experience that should be dealt with as a priority. This one aspect can foreseeably have the biggest part in improving the Firefox experience. This start-up time can not be measured by this tool. It would have to start as soon as the Firefox icon is pressed also. This tool, 'Troubleshoot Mode' becomes available after the browser is open. I have not tinkered with the Troubleshoot Mode as I expect that it would not have this capability. However, I do want you to know that I will use the Troubleshoot Mode when test tabs.
P.S. I am using the word show in place of proof. I am just winging it but I can see a poor browser performance all over. What we have said here is that even without the profiles putting a burden on performance the Firefox browser is going through some lackluster times. I do not know what else to say if I can't help!
Thanks for your time!
I called for more help.