| -rw-r--r-- | bin/kdepim/WhatsNew.txt | 3 |
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 | |||
| 15 | This is fixed. | 15 | This is fixed. |
| 16 | Example: | 16 | Example: |
| 17 | Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. | 17 | Before saving a 600k file KA/Pi did consume 21.7 Meg of Ram. |
| 18 | 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. | 18 | 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. |
| 19 | Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. | 19 | Now KA/Pi is consuming on saving the same data 22.0 Meg of Ram during the save process. |
| 20 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. | 20 | Note: The memory usage of KA/Pi after the data is loaded/saved has not changed. |
| 21 | The saving of data may be a bit slower now. | ||
| 21 | 22 | ||
| 22 | Fixed memory usage problems in KO/Pi: | 23 | Fixed memory usage problems in KO/Pi: |
| 23 | When KO/Pi did save the data to file, it did not release the used buffers after saving. | 24 | When KO/Pi did save the data to file, it did not release the used buffers after saving. |
| 24 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. | 25 | The used buffer was released after saving the next time, but there was new buffer space allocated again on that save operation. |
| 25 | This is fixed. | 26 | This is fixed. |
| 26 | Example: | 27 | Example: |
| @@ -34,12 +35,14 @@ Two (of six) buffers are removed completely. | |||
| 34 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. | 35 | The remaing four buffers are now downsized after not using the agenda view for 45 seconds. |
| 35 | 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. | 36 | 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. |
| 36 | 37 | ||
| 37 | Worst case example ( for a maximum size agenda content): | 38 | Worst case example ( for a maximum size agenda content): |
| 38 | 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. | 39 | 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. |
| 39 | 40 | ||
| 41 | 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. | ||
| 42 | |||
| 40 | Summary: | 43 | Summary: |
| 41 | Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. | 44 | Many memory wasting problems of KA/Pi and KO/Pi fixed such that it is better to use on the Zaurus. |
| 42 | 45 | ||
| 43 | ********** VERSION 2.1.12 ************ | 46 | ********** VERSION 2.1.12 ************ |
| 44 | 47 | ||
| 45 | KO/Pi: | 48 | KO/Pi: |