Chris Tilbury wrote:
> This is, of course, something that isn't addressed by either a
> transaction log or a stripe. You'd need to make a logged, mirrored,
> stripe. This is going to be quite expensive in terms of hardware.
I don't agree fully here. Cache filesystems are different from normal
filesystem. If one disk fails it does not matter much loosing the
contents of that disk, as long as the contents of the other disks are
not affected. Especially if the gain from not using mirroring is the
double number of available disks spindles (and space) for the same
price.
The same applies to if a machine crashes & reboots. It does not matter
if you loose some of the cached files.
Right now there is work going on for optimising Squid for very high
loads. Keep your eyes open for changes in 1.2.
Areas beeing looked into:
* How to handle a (to) fast network
* How to balance the load on many disks
* I/O operation pattern used by Squid.
And there is also work being made on building a custom filesystem model
suitable for caching, to get rid of much of the overhead assosiated with
a standard filesystem. Unfortanetly only performance are looked at, not
so much crash recovery.
--- Henrik Nordström Sparetime Squid HackerReceived on Mon Sep 14 1998 - 23:54:23 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:42:01 MST