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

List:       kde-devel
Subject:    Re: KHTML memory usage.
From:       Oliver Stieber <oliver_stieber () yahoo ! co ! uk>
Date:       2005-06-17 14:25:58
Message-ID: 20050617142558.47514.qmail () web26202 ! mail ! ukl ! yahoo ! com
[Download RAW message or body]


--- Allan Sandfeld Jensen <kde@carewolf.com> wrote:

> On Friday 17 June 2005 15:33, Oliver Stieber wrote:
> > Other tabs, pages in other windows that haven't
> been
> > looked at for hours that kind of thing, you could
> ben
> > extend the idea so that doms for
> previously-visited
> > pages are cached just like Safari and dropped when
> > they become a burdon on the system.
> > 
> Don't go there... This is problems already handled
> by the kernel. Things that 
> have not been used for a while are swapped to disk
> when memory pressure rise. 
> At best we could have some handle to be called when
> the kernel wants to swap 
> and compress/clean the data first, but this would be
> OS specific.
> 
<rant>
what a load of rubbish, my pc frequently grinds to a
hault because i forgot to close some konqueror tabs, 
decompressed jpegs and parsed html dom's are probably
(I've tried to find out but appear to have hit a brick
wall) many times larger than plain html and jpegs.
If khtml managed it's memory usage properly instead of
 being lazy and (oh the kernel manges that kind of
stuff) then there would be no need to the kernel to
trash swap space when I start to run out of memory,
what happenes when I run out of swapspace?
</rant>

Caching should be 'very' easy to implement and will
reduce kde bloat. (HINT: it already done for pages in
the history)

Hell, I may even be able to use kde on a laptop with
64mb of ram.


> You also have to realize that reparsing the page can
> also mean refetching 
> parts and reexecute scripts. This mean the page you
> come back might not the 
> same anymore.
> 

I'm sure I can work out which pages aren't sensible to
drop and which pages are, as I said desciding which
pages to drop is easy, it just a case of how much
memory is used by pages or images that could be
dropped out to cache.

Even refecting the odd image shouldn't be too much of
the problem (obvoiusly it would be possible to disable
this behaviour)

> `Allan
> 
> > > Visit
> http://mail.kde.org/mailman/listinfo/kde-devel#unsub
> to unsubscribe <<
> 



	
	
		
___________________________________________________________ 
Yahoo! Messenger - NEW crystal clear PC to PC calling worldwide with voicemail \
http://uk.messenger.yahoo.com  
> > Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<


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