Hello all,

I must also chime in on what has certainly felt like a significant performance 
loss that has crept into the FF engine. I went through the prior 
troubleshooting steps as well, but found the biggest 'problem' was continued 
use of the 32-bit version. Most all performance problems went away when I 
started utilizing the 64-bit version, so that might be worth a test?

In hind-sight, the explosive advent of multimedia driven sites, combined with 
add-on resource utilization, and the limitation of 2GB RAM per a 32-bit 
application was apparently more than it could readily handle with some of the 
more recent (~2 years) engine changes. Firefox was constantly freezing while 
running garbage collection for seconds at a time; while unfortunate, this is 
necessary, lest it try to use more RAM than a 32-bit application is allowed, 
and gets forcibly terminated by the O/S task scheduler.


I'm concerned, however, that this is a band-aid style approach. With Firefox 
now running multiple processes with multiple tabs, and with the RAM usage 
increasing on some new builds, I'm concerned that Firefox may shortly be as bad 
as Chrome with resource utilization.

Right now I have 5 Firefox windows open, with 7, 8, 8, 4, and 3 tabs open, 
respectively. There are 7 instances of firefox.exe running, with a memory 
Private Working Set allocation ranging from 202MB to 698MB. Total 3,366MB 
private usage. I'm only actively using about 3 of these tabs; the others are 
for reference purposes, or projects for when I get more than a few spare 
minutes at a time.

Chrome is worse: My wife uses Chrome on her personal laptop and regularly hits 
the paging file with only 2 windows open and about a dozen tabs scattered 
between them. The laptop has 6GB of RAM, yet Chrome has at least 20 processes 
running, and in excess of 4.5GB total RAM utilization in the example above. 
Chrome obviously can't manage its resource utilization well enough to keep 
comfortably within that space. While Firefox is installed and up-to-date, she 
won't use it because she doesn't like the constant changes to work-flow.

I continue to use, support, and deploy Firefox at my office because we have a 
large quantity of resource-constrained machines. Chrome tests have always gone 
very poorly for the reasons stated above. I've stuck with older builds of 
Firefox because they work very well, given the technical constraints. Several 
sites are starting to not support the older version in our labs, I'm not 
looking forward to the next upgrade.


I'm not saying that Firefox shouldn't be innovating, but if we continue in a 
direction that appears we're copying Chrome, we're going to lose sense of 
uniqueness and BECOME Chrome. I don't feel that is good for anybody.



<Message trimmed for length>



Stephen Koppes -- At Work
Network Administrator & Instructor
Penn Commercial Business/Technical School
242 Oak Spring Road
Washington PA 15301
Email: [email protected]<mailto:[email protected]>
Office: 724.222.5330 ext.338



________________________________

Confidentiality Notice: This electronic communication and any attachments 
hereto contain confidential information from Penn Commercial, Inc. This 
information is only for use by the intended recipient and use by any other 
party is not authorized. If you are not the intended recipient, or believe that 
you have received this electronic communication in error, you are hereby 
notified that any disclosure, copying, distribution or the taking of any action 
in reliance on the contents of this communication or its attachments is 
strictly prohibited. If you have received this electronic communication in 
error, please delete it from your system and notify us immediately by telephone 
at (724)222-5330 or by reply electronic mail to the person from whom this 
message was received. Thank you.
_______________________________________________
Enterprise mailing list
[email protected]
https://mail.mozilla.org/listinfo/enterprise

To unsubscribe from this list, please visit 
https://mail.mozilla.org/listinfo/enterprise or send an email to 
[email protected] with a subject of "unsubscribe"

Reply via email to