Amos:
thank you very much. i appreciate you if give me some detail.
2008/3/28, Amos Jeffries [EMAIL PROTECTED]:
Ah a few problems with COSS. Firstly it does not handle large objects
very well.
Secondy its reload requires reading into memory the entire cache_dir
slice by slice. Which is
Felix New wrote:
Amos:
thank you very much. i appreciate you if give me some detail.
2008/3/28, Amos Jeffries [EMAIL PROTECTED]:
Ah a few problems with COSS. Firstly it does not handle large objects
very well.
Secondy its reload requires reading into memory the entire cache_dir
slice by
Felix New wrote:
thanks for your reply
1. the version i used is 2.6.STABLE19
$ squid/sbin/squid -v
Squid Cache: Version 2.6.STABLE19
2. the os is red hat enterprise edition 4 update 4, and the file
system of cache dir is ext3, cache_dir is coss:
the cache_dir line in squid.conf:
cache_dir
thanks for your reply
1. the version i used is 2.6.STABLE19
$ squid/sbin/squid -v
Squid Cache: Version 2.6.STABLE19
2. the os is red hat enterprise edition 4 update 4, and the file
system of cache dir is ext3, cache_dir is coss:
the cache_dir line in squid.conf:
cache_dir coss /cache/coss 8000
hi all,
i have used aufs file system for a few days and that is very good.
but i encounter a question when i chang the aufs to coss: the cpu load
is very very high(100% nearly) when i rotate the squid access log file
with command 'squid -k rotate', and can not fall down.
i google that and
Felix New wrote:
hi all,
i have used aufs file system for a few days and that is very good.
but i encounter a question when i chang the aufs to coss: the cpu load
is very very high(100% nearly) when i rotate the squid access log file
with command 'squid -k rotate', and can not fall down.
