[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Experiences, speed issues, bugs...
From:       John Califf <jcaliff () compuzone ! net>
Date:       2000-12-19 23:59:42
[Download RAW message or body]

Jelmer Feenstra wrote:
> 
> On Tuesday 19 December 2000 21:14, Richard Bos wrote:
> > Jelmer,
> >
> > speed may be an issue for you as 64MB of memory is not enough.
> > I've 64MB more than you, (350MHz PII) and have no problem
> > with speed.  So time for a memory upgrade??
> 
> Well, my point is that some of the speed issues are actually not present in
> let's say, netscape. When I select text in netscape, it's not as sluggish as
> it is within konqueror. Also, the displaying itself of the webpage (seen the
> most when backing through previous visited sites) is slow, sometimes you can
> follow the building of the display from the top to the bottom. The
> highlighting of text, going back through visited pages and redrawing stuff is
> all a lot faster if I try it in IE when running win98. I just wondered what
> could be the cause of this.
> 

I agree.  64 megs. of ram should be more than enough to get *good*
performance with kde2 in normal situations - using it as a desktop
client for web surfing, home/small office productivity, games and even
software development. 

The problem with konqueror and long lists, or any long set of items
enclosed with tags, is something I complained about months ago.  It's a
design issue in how tags are parsed and pages are rendered.  Evidently
everything has to be read into memory before anything is rendered if
enclosed with a tag set.  Netscape does not have this problem and
doesn't choke on pages with long lists of text or images.  Koffice apps
that parse long lists have the same problem Konqueror has - namely
kword.  It chokes on even moderately large files.  This has very little
to do with the amount of ram and increasing ram is NOT the solution to
this structural/design issue.  The solution is loading first an outline
of the structure of the document and then filling in content or details
as needed, and folding inactive content back into the outline, or
something similar.  This way the entire content doesn't have to be
loaded into memory and parsed in detail for the app to show the current
content.  Only the current content should be parsed in detail, IMHO.

I only have 32 megs of RAM and *develop* koffice apps with this
machine.  Don't laugh too hard!  Sure, I need a memory upgrade and hope
to get one after Christmas.  But the only problem I have is with
extremely large source files (over 100k) taking a while during the
compile phase only and using a lot of swap.  Actually the performance of
konqueror is very good except with the long lists problem described
above, and most kde apps are quite responsive.  For example, right now
I'm running the kde desktop, netscape mail, konqueror, konsole, half a
dozen active panel apps - no problem. (Plus all 6 of the standard text
consoles open outside of X).

John
 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]