Amiga.org
Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: fragment on January 18, 2004, 05:47:31 PM
-
Okay, I've been running on this configuration for about 6 months now and I was wondering is it possible to utilise the 64MB fastram better. I have about 55-63MB fastram free depending what software I'm running.
Is it possible for example to cache the icons in directories so they don't need to be loaded from the HD everytime I reopen the directory in WB? Also, is it possible to cache the libraries in use? For example running "wget" without options always takes about 4 seconds (uses ixemul.library) and seems to load it from the HD.
I'm already running BlazeWCP and fblit. So are there any other useful patches I should install? I'm using 060+AGA and AOS 3.5 (with boingbags).
-
Libraries that are in use, are in memory,and normally they stay there till all
apps useing them terminate AND the user calls "avail flush".
Cacheing them makes no sense.
-
Icon imagery isn't cached. Even default icons read the env:sys/def_xxx.info files.
I've often thought about a patch for the icon.library for this purpose that would store the actual image data into some sort of LRU cache that was user sizeable.
You would always have to open the icon file to access the tooltypes and so forth, but cacheing the imagery would speed it up considerably, especially if you store it in a method best suited for the graphics hardware.
You just need to make sure your cacheing mechanism can catch any changes made to the icon.
-
Kronos wrote:
Libraries that are in use, are in memory,and normally they stay there till all
apps useing them terminate AND the user calls "avail flush".
OR the OS needs to allocate the memory to some other task - in which case any unused libraries are flushed. So, they are already cached.
Rather than just caching icons, wouldn't it be better to run a disk cache patch?
Chris
-
chris wrote:
Rather than just caching icons, wouldn't it be better to run a disk cache patch?
Chris
A dedicated cache for the icon image data (stored in decoded format best suited for the display) could outperform a generic disk cache considerably. On some systems, the images could even be held in VRAM, for example.