Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 Mar 2002 18:18:48 -0600
From:      "Matthew D. Fuller" <fullermd@over-yonder.net>
To:        "Jeremy C. Reed" <reed@reedmedia.net>
Cc:        freebsd-chat@freebsd.org
Subject:   Re: Taming Netscape Navigator?
Message-ID:  <20020302181848.D3880@over-yonder.net>
In-Reply-To: <Pine.LNX.4.43.0203020853270.2796-100000@pilchuck.reedmedia.net>; from reed@reedmedia.net on Sat, Mar 02, 2002 at 09:23:21AM -0800
References:  <3C7FB956.18428.510B414@localhost> <Pine.LNX.4.43.0203020853270.2796-100000@pilchuck.reedmedia.net>

next in thread | previous in thread | raw e-mail | index | archive | help

On Sat, Mar 02, 2002 at 09:23:21AM -0800 I heard the voice of
Jeremy C. Reed, and lo! it spake thus:
> 
> > There's no real file I/O happening (unless you're really short on RAM and
> > thrashing the swap), it's just being painfully slow about calculating out
> > the table.
> 
> It is also slow for me to just look at long 100KB webpages that have very
> little formatting (and no tables).

It's not instantaneous, but I haven't noticed any big delays on pages
that size (certainly not relative to what ever other graphical browser
has).


> > It's a lot slower rendering big tables (like 10 vs. 30 minutes, for some
> > *BIG* tables I've passed through 'em), and isn't near as snappy overall,
> 
> You are patient. After a couple minutes, I log on remotely to kill all the
> netscapes.

No, it was a meg and a half (of very compact HTML) of one big table that
I *HAD* to get information out of.  Patience is irrelevant when necessity
comes into the equation  :)

Why log on remotely?  I just kill it locally if I have to (which isn't
too often...  it rarely locks up unless it's doing something I want done,
which it will eventually finish, and the rest of the time crashes close
it neatly :)


> But what about "controlling" netscape?
> 
> How or why does it make my X and/or window manager unusable?

Because it nails the CPU up to the wall.

I nice it to +10, which makes a slight difference.  Using a dual-CPU
workstations makes a heck of a lot more, since I can nail it up to the
wall and keep playing mp3's, and still have the majority of a CPU
available for interactive response.

I fully intend to never use a single-CPU system for a workstation ever
again.  I like the safety net.



-- 
Matthew Fuller     (MF4839)     |    fullermd@over-yonder.net
Unix Systems Administrator      |    fullermd@futuresouth.com
Specializing in FreeBSD         |    http://www.over-yonder.net/

"The only reason I'm burning my candle at both ends, is because I
      haven't figured out how to light the middle yet"

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-chat" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020302181848.D3880>