Firefox/Feature Brainstorming:Performance: Difference between revisions
(→Performance: auto-loaded extensions) |
(Adding a new request) |
||
(3 intermediate revisions by 3 users not shown) | |||
Line 3: | Line 3: | ||
<tr><th>Specific features</th> | <tr><th>Specific features</th> | ||
<th width="20%">References</th></tr> | <th width="20%">References</th></tr> | ||
<tr><td> | |||
Make jQuery's code native. sounds crazy :) | |||
</td><td></td></tr> | |||
<tr><td> | <tr><td> | ||
Line 151: | Line 155: | ||
</td><td> | </td><td> | ||
https://addons.mozilla.org/firefox/2110/ | https://addons.mozilla.org/firefox/2110/ | ||
</td></tr> | |||
<tr><td> | |||
* An other part of the way to improve the start delay is checking for updates less frequently, not all startups, or doing this check with an asynchronous way. By unchecking the preference to check for updates, the startup is more or less instantly on my windows. | |||
</td><td> | |||
</td></tr> | </td></tr> | ||
Line 158: | Line 168: | ||
So my suggestion would be: if pages are invisible (e.g. inside inactive tabs), let them sleep temporarily until the page becomes visible again. Or at least pause those Flash movies temporarily. | So my suggestion would be: if pages are invisible (e.g. inside inactive tabs), let them sleep temporarily until the page becomes visible again. Or at least pause those Flash movies temporarily. | ||
</td><td> | </td><td> | ||
[[Firefox should save energy]] | |||
</td></tr> | </td></tr> | ||
Line 181: | Line 191: | ||
</td><td> | </td><td> | ||
</td></tr> | </td></tr> | ||
<tr><td> | |||
'''Radical Change? Maybe Not?''' | |||
O.K. I know it's Tiring Hearing/Viewing this, but I'll Keep it Short as I can:<br> | |||
System Resources are a Major Factor to Consider. Firefox Hogs a lot of CPU it Doesn't Necessarily need Sometimes. It Also Hauls/Hangs/Stalls Huge amounts of CPU when Apparently Doing Nothing (Bug? Leak?). It Also Hogs a lot of Virtual Memory, More then Twice that of IE. And although, it doesn't Take long for Firefox to Load, it IS Noticeably Slow. Greater Acceleration is Needed/Appreciated In this area. Perhaps JAVA has A lot to do with some of the Downsides/Shortcomings of Firefox. Is a Complete/New Compilation of Firefox Under a More Favorable Language, Out of the Question? Perhaps C++? OR, Is it at all Possible to overcome, this, Shortcoming? | |||
Pardon, I would also Like to add a Couple more things As I believe is relevant and Don't seem to see another place for these in terms of, Sections: | |||
If a page stalls in Firefox, you must restart the Page again for it to Load Correctly. (Not necessarily cached. Be better if Firefox can just load the missing parts only, then go back and recheck the ones that were previously loaded.) | |||
Links within sites do not load in a separate process. I have to wait for the main page to load first before any of the other Links I click even try to begin to Load.(In IE, I don't have to wait till the main page loads so I can check the other links within the site. It's a big deal for me.) | |||
I have also Noticed this: | |||
Clicking the Scroll button on the mouse sends more "load" to the load bar. (It gives a false sense of how much is Actually left to load.) | |||
<br>*Sorry, That probably doesn't go here.* | |||
Welp, that Said any:<br> | |||
Objections?<br> | |||
Concerns?<br> | |||
Mitigation?<br> | |||
A More Informative Explanation as to Why this can't, or has yet to be Implemented? | |||
</td><td> | |||
N/A | |||
</td></tr> | |||
</table> | </table> |
Latest revision as of 16:55, 26 September 2012
« Firefox/Feature Brainstorming
Specific features | References |
---|---|
Make jQuery's code native. sounds crazy :) | |
Make it possible to have firefox started as a new process with a switch (firefox.exe -np) to be able to have two instances running in case you are testing something that crashes the browser often while you are in some deep and nested back-end at the same time. it is very annoying that when it crashes all is lost. Yes - i could use another browser for the back-end stuff but why would i? firefox.exe -no-remote -P otherprofile Note: This is partly already possibly with the environment variable MOZ_NO_REMOTE set to 1. |
Like you can have multiple instances of IE running |
Be the fastest browser on the market, not only on "fat" desktops, but also on bargain desktops with only 256MB of RAM. More other, when firefox is reduced on the taskbar, the memory use doesn't decrease on the opposite of Opera and....IE7.Reference:(in french)[1] | |
Try to implement an internal memory manager. It should, for example, pre-allocate about 10% of ram memory and try to operate within that memory. All calls to "free()" should release memory to this global memory pool and all calls to "malloc()" must allocate memory from this memory pool. If properly implemented, we can even reduce the overheads that may arise due to such an implementation. |
Keep to improve the browsing velocity .Reference:[2] |
One feature I would like to see is faster startup times and less memory hogging as at the moment I think that ff takes a long time to boot up the 1st time but less time after that so I think a preloader would be a good idea and I also agree in trying to sandbox the browser/extensions to a defined amount of memory Therefore make the browser work faster. | n/a |
Improve browser launch time on both Windows and Mac OS X. Currently IE and Safari launch much more efficiently, making it more sensible to open one of those browsers when quickly looking something up. Enduring the sluggish launch time again and again makes for an irritating experience. |
n/a |
Integrate a FF Preloader into the program. Currently the Preloader for Firefox 1.0 doesn't work for 2.0. A preloader option within FF that allows the user to choose whether to preload certain parts of FF could improve the boot time dramatically. |
n/a |
At the very least, bring up a UI as quickly as possible. Show the splashscreen while loading. Often I find I don't know whether Firefox has started up and start up multiple copies. |
n/a |
Bring speed up to par with Safari/Opera on the Mac platform. Perhaps bring project into XCode/Objective-C/Cocoa? The Cocoa API is much more feature complete than the Carbon API, since the latter is more of a carry over from MacOS 9. With Cocoa, things like integerated spell checking would come 'free', since they are associated with the widgets being used. |
n/a |
Hardware accelerated graphics (perhaps use the Vista/Mac OS X/AIGLX/XGL engines to do the acceleration for us) |
n/a |
Make the javascript engine less cpu hungry. On a security and programmation site, I saw: the javascript engine of firefox is a nice untidiness, what is a security and perfomance failing. |
n/a |
Do more caching of the DOM. E.g. stacking several PNG-Images with alpha channel slows down the browser dramatically, even for unrelated DOM changes. |
n/a |
Make the textarea performance better. Often, even on fast machines, I can type faster than the text appears. This doesn't happen all the time, but does often enough. As it catches up to me, I see all of the text in the textarea being cleared and flashing up for each character typed. |
n/a |
It is very annoying to be typing into a text box and have the browser go unresponsive for a few seconds while in the middle of typing. This is caused by Javascript in other windows (like gmail) waking up and using the network. Threading needs work to fix this. |
n/a |
Put each document into an independent process (not thread: separate forked process) so that:
| |
Include a language-neutral VM for a back-end for javascript. The benefits are quite significant, and include: JIT compling, with caches of compiled code (done when the VM is not busy); a better sandboxing model for compile-time overruns and exception handling; better threading model for managing multiple windows and tabs; language-neutral interface for extending or replacing the runtime language (i.e. changing it from something like "javascript-1.7" to "moz-cli-1.0", so that languages like Ruby and Python could be compiled into the cli); easier to add libraries of code to the base distribution or from external sources (code libraries that people could download to their computers and use for certain sites); the introduction of a unified object/exception/type model. Perhaps less important reasons include: businesses might be a little happier because their code wouldn't be completely "transparent" as it travels across the net if it's possible to send it already compiled to a person's computer; it might make it possible to add extensions, like signed code or an abstract threading model. |
n/a |
Now multi-core CPUs are becomming standard it makes sense to improve multi-threading. Javascript or rendering on one tab should not lock up other tabs, for example. Even within a tab, image decoding, scripting, plugins and HTML rendering could all be separated. |
n/a |
Consider implementing IEView and IETab extensions funcitonality in FF itself. Many web pages (e.g. some online e-mail access services) still require the user to be running IE so a way for FF users to view those pages wityhout having to find out and install those extensions would be extremely useful. |
n/a |
Remove memory leaks (e.g. try using Firefox on the Typo3 Backend - you'll have to restart FF about once per hour, if you seriously use it) |
n/a |
Make Firefox more crash resistant. I don't really know if it is the FF core which causes the crashes or one of the Extensions I run. Additional idea: Let Extensions run in a sandbox so they can't crash Firefox any more. Maybe that sandbox could also guard against unsafe Extensions which may try to compromise your computer. |
n/a |
| |
kind of like this: https://addons.mozilla.org/firefox/2110/ | |
| |
Sleep invisible pages! Especially Flash movies! | |
General tasks | |
|
n/a |
|
Keep to improve the browsing velocity .Reference:[3] |
Make the above extensions automatically loaded when they are needed, but not loaded initially. This saves memory and speeds up startup time and page load time. | |
Radical Change? Maybe Not? O.K. I know it's Tiring Hearing/Viewing this, but I'll Keep it Short as I can: Pardon, I would also Like to add a Couple more things As I believe is relevant and Don't seem to see another place for these in terms of, Sections: If a page stalls in Firefox, you must restart the Page again for it to Load Correctly. (Not necessarily cached. Be better if Firefox can just load the missing parts only, then go back and recheck the ones that were previously loaded.) Links within sites do not load in a separate process. I have to wait for the main page to load first before any of the other Links I click even try to begin to Load.(In IE, I don't have to wait till the main page loads so I can check the other links within the site. It's a big deal for me.) I have also Noticed this: Clicking the Scroll button on the mouse sends more "load" to the load bar. (It gives a false sense of how much is Actually left to load.)
Welp, that Said any: |
N/A |