|
|
1.
|
|
|
<h1>KDE Performance</h1> You can configure settings that improve KDE performance here.
|
|
|
|
|
<h1>KDE Performance</h1> You can configure settings that improve KDE performance here.
|
|
Translated and reviewed by
Malcolm Hunter
|
|
|
|
Located in
kcmperformance.cpp:48
|
|
|
2.
|
|
|
Konqueror
|
|
|
|
|
Konqueror
|
|
Translated and reviewed by
Malcolm Hunter
|
|
|
|
Located in
kcmperformance.cpp:55
|
|
|
3.
|
|
|
System
|
|
|
|
|
System
|
|
Translated and reviewed by
Malcolm Hunter
|
|
|
|
Located in
kcmperformance.cpp:58
|
|
|
4.
|
|
|
<h1>Konqueror Performance</h1> You can configure several settings that improve Konqueror performance here. These include options for reusing already running instances and for keeping instances preloaded.
|
|
|
|
|
<h1>Konqueror Performance</h1> You can configure several settings that improve Konqueror performance here. These include options for reusing already running instances and for keeping instances preloaded.
|
|
Translated and reviewed by
Malcolm Hunter
|
|
|
|
Located in
kcmperformance.cpp:83
|
|
|
5.
|
|
|
Disables the minimization of memory usage and allows you to make each browsing activity independent from the others
|
|
|
|
|
Disables the minimisation of memory usage and allows you to make each browsing activity independent from the others
|
|
Translated and reviewed by
Malcolm Hunter
|
|
|
|
Located in
konqueror.cpp:35
|
|
|
6.
|
|
|
<p>With this option activated, only one instance of Konqueror used for file browsing will exist in the memory of your computer at any moment, no matter how many file browsing windows you open, thus reducing resource requirements.</p><p>Be aware that this also means that, if something goes wrong, all your file browsing windows will be closed simultaneously</p>
|
|
|
|
|
<p>With this option activated, only one instance of Konqueror used for file browsing will exist in the memory of your computer at any moment, no matter how many file browsing windows you open, thus reducing resource requirements.</p><p>Be aware that this also means that, if something goes wrong, all your file browsing windows will be closed simultaneously</p>
|
|
Translated by
Malcolm Hunter
|
|
|
|
Located in
konqueror.cpp:38
|
|
|
7.
|
|
|
<p>With this option activated, only one instance of Konqueror will exist in the memory of your computer at any moment, no matter how many browsing windows you open, thus reducing resource requirements.</p><p>Be aware that this also means that, if something goes wrong, all your browsing windows will be closed simultaneously.</p>
|
|
|
|
|
<p>With this option activated, only one instance of Konqueror will exist in the memory of your computer at any moment, no matter how many browsing windows you open, thus reducing resource requirements.</p><p>Be aware that this also means that, if something goes wrong, all your browsing windows will be closed simultaneously.</p>
|
|
Translated by
Malcolm Hunter
|
|
|
|
Located in
konqueror.cpp:46
|
|
|
8.
|
|
|
<p>If non-zero, this option allows keeping Konqueror instances in memory after all their windows have been closed, up to the number specified in this option.</p><p>When a new Konqueror instance is needed, one of these preloaded instances will be reused instead, improving responsiveness at the expense of the memory required by the preloaded instances.</p>
|
|
|
|
|
<p>If non-zero, this option allows keeping Konqueror instances in memory after all their windows have been closed, up to the number specified in this option.</p><p>When a new Konqueror instance is needed, one of these preloaded instances will be reused instead, improving responsiveness at the expense of the memory required by the preloaded instances.</p>
|
|
Translated by
Malcolm Hunter
|
|
|
|
Located in
konqueror.cpp:58
|
|
|
9.
|
|
|
<p>If enabled, an instance of Konqueror will be preloaded after the ordinary KDE startup sequence.</p><p>This will make the first Konqueror window open faster, but at the expense of longer KDE startup times (but you will be able to work while it is loading, so you may not even notice that it is taking longer).</p>
|
|
|
|
|
<p>If enabled, an instance of Konqueror will be preloaded after the ordinary KDE startup sequence.</p><p>This will make the first Konqueror window open faster, but at the expense of longer KDE startup times (but you will be able to work while it is loading, so you may not even notice that it is taking longer).</p>
|
|
Translated by
Malcolm Hunter
|
|
|
|
Located in
konqueror.cpp:67
|
|
|
10.
|
|
|
<p>If enabled, KDE will always try to have one preloaded Konqueror instance ready; preloading a new instance in the background whenever there is not one available, so that windows will always open quickly.</p><p><b>Warning:</b> In some cases, it is actually possible that this will reduce perceived performance.</p>
|
|
|
|
|
<p>If enabled, KDE will always try to have one preloaded Konqueror instance ready; preloading a new instance in the background whenever there is not one available, so that windows will always open quickly.</p><p><b>Warning:</b> In some cases, it is actually possible that this will reduce perceived performance.</p>
|
|
Translated by
Malcolm Hunter
|
|
|
|
Located in
konqueror.cpp:73
|
