Re: considering how slow and bloated every mozilla app is..

On 30/08/2009 18:18, chris hofmann wrote:
> Martijn wrote:
>> On Sun, Aug 30, 2009 at 6:53 PM, gperry<[email protected]> wrote:
>>> On 30/08/2009 16:15, Boris Zbarsky wrote:
>>>
>>>> That said, do you have specific numbers/examples to support your
>>>> "bloated" assertion?
>>> FF is currently at 150meg, it'll 300 before long and I'll have to close.
>>> Those figures are normal for FF atm.
> doing what?
> not saying this to be defensive. detailed and specific examples and test
> beyond what you list below is what we need to take actionable steps.
Normal browsing over the course of a few hours, with never more than 3 
or 4 tabs open. Sites include ebay, some php and vbb forums and some 
blogs, normal stuff, normal use. Now at 150 meg again, after having 
restarted it about 10 minutes ago. It starts at 50meg rises quickly, 
stays at about 150, then on occasional feature rich page it'll go to 
300, and important it never sheds the memory when you navigate away.

(while I was typing this, thunderbird seized up, whited out and become 
unresponsive to key presses for 30 seconds. 30 secs after that, my 
remote calendars events redrew on the today page.)

>>> TB and Lightning are 160meg. Outlook is running along side it with
>>> the same
>>> imap accounts and remote calendars and it's just over 35meg (and it's
>>> way
>>> faster).
>>>
>>>
>>> For that matter, do you have specific issues that
>>>> you describe as "slow"? A general "slow" is not an actionable item.
>>>>
>>>> -Boris
>>> -Page laods are slow in FF, slower than even IE. Chrome and Opera
>>> make FF
>>> look like a joke.
>>>
> which "pages"?
> by how much?
Every page. Some times it appears to load faster, but the time taken 
before the page actually becomes available to me to scroll etc, is much 
longer. This is again down the the sheer cpu resources that FF needs to 
load a page.
>>> -javascript performance is horrible
> on which bench mark or page?
>>> -When pages are loading, the rest of the interface is unresponsive.
>>> In fact
>>> is takes so much processor priority as too jam up the entire operating
>>> system.
> which pages? good test cases needed/wanted.
Again, every page, compare page loads in FF to opera, chrome and IE, 
you'll see cpu hit 80-90% on every page in FF, while the rest barely 
break a sweat.
>>> -'complex' webpages jam up the browser, leading to slow scrolling and
>>> slow
>>> inteface. By 'complex' I mean a little bit of javascript or an image
>>> table
>>> with a few effects, or some text decoration here and there.
>>>
> which pages or test cases show this? can you point at one or put one
> together?
Next time I come across one I'll post it here.