Re: KATE too slow when editing large files

On Tuesday 06 August 2002 03:28, Manuel Lemos wrote:
> I use SuSE 7.1 and Kate is also very unstable. Often it crashes when I
> dare to split views, so much that I avoid doing that. I am not sure if
> the backtrace would help as a bug report because other than it is not
> very easy to describe a precise sequence to reproduce the problem.

What KDE and Kate versions would that be? We are currently discussing KDE 
3.0.6 or 3.1 a1.

> But back to the original subject, I am very surpised of how much memory
> Kate eats from the system. For instance, just loading a 8Kb text file,
> makes Kate take 15Mb or RAM. Why does it take so much memory? What is it
> doing with all that memory? Of course once real memory is exhausted it
> starts using virtual memory and everything becomes tad slow.

I think the original subject was slow reaction to typing into large perl 
files?

For the memory issue, look at what is shared, and try seeing what opening an 
extra file of 8kb of text does to the memory usage.

An example from here: Kate is open, the SIZE in top says 63936 (Kb). I open a 
file of 11K, and SIZE raises to 64280. That means opening the file added 344K 
to the memory usage. This includes the editor component for that file, it's 
plugins, the file data + the data used internally for highlightning, 
bookmarks etc, and this is with full debugging enabled in the binary (the 
sizes includes a lot of strings and data for the debugger). It should be 
signiificantly less without that.

Yes Kate uses memory, but it does so for a reason: providing the best possible 
editing environment we can.

(Hmm, someone have an optimized Kate? actually analyzing the memory usage 
would be kinda interessting...)

-anders