summaryrefslogtreecommitdiffabout
authorzautrix <zautrix>2005-07-06 09:35:19 (UTC)
committer zautrix <zautrix>2005-07-06 09:35:19 (UTC)
commit4ac63cce98fabb59a47970baa2906b2fe8d0f2b0 (patch) (side-by-side diff)
tree8dbbbd1526c088eaf55b5089db761dfc705c3ffc
parent38c8ca3f376451c072650fad8964adbbc513a105 (diff)
downloadkdepimpi-4ac63cce98fabb59a47970baa2906b2fe8d0f2b0.zip
kdepimpi-4ac63cce98fabb59a47970baa2906b2fe8d0f2b0.tar.gz
kdepimpi-4ac63cce98fabb59a47970baa2906b2fe8d0f2b0.tar.bz2
fixxxx
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--bin/kdepim/WhatsNew.txt3
1 files changed, 3 insertions, 0 deletions
diff --git a/bin/kdepim/WhatsNew.txt b/bin/kdepim/WhatsNew.txt
index ea49c2c..d6b2dc7 100644
--- a/bin/kdepim/WhatsNew.txt
+++ b/bin/kdepim/WhatsNew.txt
@@ -15,12 +15,13 @@ When saving data KA/Pi did consume a lot of memory for the data parsing during t
This is fixed.
Example:
Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram.
When saving KA/Pi did consume 28.6 Meg of Ram. That causes a crash on the Zaurus because there was no memeory left in the system.
Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process.
Note: The memory usage of KA/Pi after the data is loaded/saved has not changed.
+The saving of data may be a bit slower now.
Fixed memory usage problems in KO/Pi:
When KO/Pi did save the data to file, it did not release the used buffers after saving.
The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation.
This is fixed.
Example:
@@ -34,12 +35,14 @@ Two (of six) buffers are removed completely.
The remaing four buffers are now downsized after not using the agenda view for 45 seconds.
Such that the memory usage of KO/Pi is smaller now in general ( because 2 buffers are removed) and is much smaller when not using the agenda view. That is very important when using fastload for KO/Pi.
Worst case example ( for a maximum size agenda content):
When resizing the agenda content to a large scale, KO/Pi did use 17Meg of mem ( and did not use less memory until it was stopped). Now KO/Pi is using on the same operation only 14.3 Meg of mem and after 45 seconds not using the agenda view it uses only 9.4 Meg of mem.
+When switching to an unused Agenda view now KO/Pi is upizing the buffers again. This takes less than a second. Such that switching to Agenda view (after not using it for more than 45 seconds) is now a bit slower.
+
Summary:
Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus.
********** VERSION 2.1.12 ************
KO/Pi: