Re: Caches

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

Re: Caches
by Aaron Seigo on Sunday 17/Jun/2007, @23:55

the point of the icon cache is to speed things up. throwing them on a machine somewhere on the network seems ... counter productive.

squid helps with web browsing because it caches remote content on a system that is closer to the destination (you). integrating the icon cache with something like squid would be doing exactly the opposite, and therefore have exactly the opposite effect (e.g. slow things down).

additionally, the sort of on-disk strategies used by web cache apps are not necessarily the greatest for other work loads such as icons due to differences in access patterns. so even if squid was running locally it probably wouldn't be the best idea.

direct access to a shared local file that is tuned for icon access patterns is going to be hard to beat. and i'm really not sure what benefits a network cache would have.

i can see sharing cache files on a system serving x clients over the network (e.g. thin client setups) could be nice for disk space and disk cache friendliness ... but that's also local (to the app) and not on the network.

Related Links

·   Articles on Developer
·   Also by Aaron Seigo
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )


		"coffee? kde developers drink tea ;)" -- Dirk Mueller
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.