faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
Re: City of Largo Adopts KDE 2.1.1
by not me on Tuesday 24/Jul/2001, @00:50
|
Wow, that 11-12 MB per user surprised me. I guess X and shared libs are what is taking all my computer's RAM. How does that compare to the KDE 1 system that you guys had before?
Also, isn't it already possible to turn off things like the Quick Browser? I'm sure I saw that somewhere... |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: City of Largo Adopts KDE 2.1.1
by Krame on Tuesday 24/Jul/2001, @01:47
|
Libraries and programs are shared between all users. 11MB is for users data. There shouldn't be much difference in memory usage if you keep everything on a single server.
|
[
Reply To This | View ]
|
Re: City of Largo Adopts KDE 2.1.1
by not me on Tuesday 24/Jul/2001, @04:56
|
Yeah, I know. That's what I meant. The actual data stored by KDE in RAM is less than I thought, all the other RAM that's being taken up on my computer is from X, shared libs, and program binaries.
Actually, now that I think of it, 11MB is kind of a lot of data. That's roughly 11,000 screenfuls of text. I wonder what makes up that ~11MB per user storage space? Perhaps knowing what is in there could give some clues as to how to increase KDE's memory efficiency?
|
[
Reply To This | View ]
|
Re: City of Largo Adopts KDE 2.1.1
by Slashgeek on Monday 13/Aug/2001, @22:15
|
I wonder what makes up that ~11MB per user storage space?
Imported .doc and .xls files, what else?
|
[
Reply To This | View ]
|
|
Re: City of Largo Adopts KDE 2.1.1
by Carbon on Tuesday 24/Jul/2001, @02:23
|
Yes, it is most definetly possible to turn off the things in the menu you wanted turned off, except for "Run Command". It's in the kicker settings area in the Control Center, under the Menus tab.
Hmm, as for Kicker autorefresh, I have no idea why that should take so long. Doesn't kicker simply watch it's desktop file directory using the KDirWatcher class (sp?), which iirc uses the kernel to watch for processes. Could someone check this?
|
[
Reply To This | View ]
|
Re: City of Largo Adopts KDE 2.1.1
by foobar on Tuesday 24/Jul/2001, @04:29
|
I think the problem with Kicker is that it check for changes periodically and with 200+ people accessing the network at once, it creates a huge bottleneck. Maybe if there is some small amount of randomness in the timing, it would be less of a load on the network.
|
[
Reply To This | View ]
|
Re: City of Largo Adopts KDE 2.1.1
by georg on Tuesday 24/Jul/2001, @07:43
|
For restarting kicker, what about
dcop default kicker restart?
|
[
Reply To This | View ]
|
Re: City of Largo Adopts KDE 2.1.1
by Waldo Bastian on Wednesday 25/Jul/2001, @03:31
|
Not really randomness, but with the following lines in sharec/config/kdedrc you can tell it how often to poll.
E.g: the following configures local fs once 0.5 seconds and non-local FS once each 5 seconds, which also happens to be the default.
[General]
PollInterval=500
NFSPollInterval=5000
Cheers,
Waldo
|
[
Reply To This | View ]
|
Re: City of Largo Adopts KDE 2.1.1
by David Faure on Tuesday 24/Jul/2001, @22:45
|
Yes, the autorefresh uses KDirWatch, so he should simply install libfam and reconfigure, to get rid of the polling.
The kernel support called dnotify is currently disabled again, 'cause not working properly yet.
|
[
Reply To This | View ]
|
Re: City of Largo Adopts KDE 2.1.1
by Michael Wardle on Monday 13/Aug/2001, @18:51
|
"The kernel support called dnotify is currently disabled again, 'cause not working properly yet."
Actually, the preferred kernel support for fam is called imon, and can be obtained from
<URL:http://oss.sgi.com/projects/fam/download/>. There are others who are doing work with fam/dnotify rather than fam/imon since dnotify has made it into the standard kernel sources.
--
MICHAEL WARDLE
SGI FAM Maintainer
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
