WG: [squid-users] COSS still under developement?

2007-10-04 Thread Stolle, Martin 
 
We use coss on our production proxies with squid-2.6. It has got a really big 
performance. 

Switching to aufs wouldn't be an alternative, so we have to wait vor 3.1

Regards

Martin Stolle
-Ursprüngliche Nachricht-
Von: Henrik Nordstrom [mailto:[EMAIL PROTECTED] 
Gesendet: Donnerstag, 4. Oktober 2007 03:29
An: leongmzlist
Cc: Squid
Betreff: Re: [squid-users] COSS still under developement?

On ons, 2007-10-03 at 17:19 -0700, leongmzlist wrote:
 I remember reading somewhere coss will be removed from the 3.0 
 release, just want to make sure it's won't get abandoned since our 
 cache data is really important to us.

It's not removed, but downgraded to experimental for 3.0, with updated COSS 
support scheduled for 3.1 if there is sufficient interest in having the 
improvements forwardported.

There was talk about removing COSS from the 3.0 release as it's known to be 
unstable and not suitable for production use in squid-3, but it was then 
decided to not fork 3.0 from the 3.x tree before release and COSS stayed.

There is no plans on removing COSS from Squid as such, only the 3.0 release as 
there has not been any developer resources available to update the Squid-3 COSS 
implementation and it's far behind Sqiud-2 in that area.

Regards
Henrik


signature.asc
Description: PGP signature

[squid-users] COSS still under developement?

2007-10-03 Thread leongmzlist 

Hi,

The list has been very quiet w/ regards to the coss storage.

1. is it still being developed/maintained?
2. is it production ready?

mike

Re: [squid-users] COSS still under developement?

2007-10-03 Thread Adrian Chadd 
On Wed, Oct 03, 2007, leongmzlist wrote:
 Hi,
 
 The list has been very quiet w/ regards to the coss storage.
 
 1. is it still being developed/maintained?
 2. is it production ready?

From the reports from people using it, COSS is good enough to use for small
objects  a hundred or so kilobytes.

Give it a shot and let us know if it works or doesn't work for you.



Adrian

Re: [squid-users] COSS still under developement?

2007-10-03 Thread leongmzlist 
I remember reading somewhere coss will be removed from the 3.0 
release, just want to make sure it's won't get abandoned since our 
cache data is really important to us.


mike

At 03:58 PM 10/3/2007, Adrian Chadd wrote:

On Wed, Oct 03, 2007, leongmzlist wrote:
 Hi,

 The list has been very quiet w/ regards to the coss storage.

 1. is it still being developed/maintained?
 2. is it production ready?

From the reports from people using it, COSS is good enough to use for small
objects  a hundred or so kilobytes.

Give it a shot and let us know if it works or doesn't work for you.



Adrian

Re: [squid-users] COSS still under developement?

2007-10-03 Thread Adrian Chadd 
On Wed, Oct 03, 2007, leongmzlist wrote:
 I remember reading somewhere coss will be removed from the 3.0 
 release, just want to make sure it's won't get abandoned since our 
 cache data is really important to us.

Squid-2 won't be abandoned for quite a while. If someone wants to sponsor
forward porting and testing COSS from Squid-2 to Squid-3 then please
contact a developer directly.




Adrian

Re: [squid-users] COSS still under developement?

2007-10-03 Thread Henrik Nordstrom 
On ons, 2007-10-03 at 17:19 -0700, leongmzlist wrote:
 I remember reading somewhere coss will be removed from the 3.0 
 release, just want to make sure it's won't get abandoned since our 
 cache data is really important to us.

It's not removed, but downgraded to experimental for 3.0, with updated
COSS support scheduled for 3.1 if there is sufficient interest in having
the improvements forwardported.

There was talk about removing COSS from the 3.0 release as it's known to
be unstable and not suitable for production use in squid-3, but it was
then decided to not fork 3.0 from the 3.x tree before release and COSS
stayed.

There is no plans on removing COSS from Squid as such, only the 3.0
release as there has not been any developer resources available to
update the Squid-3 COSS implementation and it's far behind Sqiud-2 in
that area.

Regards
Henrik


signature.asc
Description: This is a digitally signed message part

Re: [squid-users] COSS still under developement?

2007-10-03 Thread Tek Bahadur Limbu 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Leongmzlist,


On Wed, 03 Oct 2007 14:57:17 -0700
leongmzlist [EMAIL PROTECTED] wrote:

 Hi,
 
 The list has been very quiet w/ regards to the coss storage.
 
 1. is it still being developed/maintained?
 2. is it production ready?


I am using COSS for some of my FreeBSD Squid proxy servers. The reason why I 
chose the COSS storage scheme was because DISKD kept on crashing repeatedly 
under high load (150 - 200 req/sec). 

I have to say that it's quite stable. Squid hasn't crashed in last 35 days 
since I deployed COSS in it. 

It seems quite fast too keeping in mind that we have a satellite link. 

Below are some of stats after deploying COSS in one of my proxies:

- 

root# squidclient mgr:info

HTTP/1.0 200 OK
Server: squid
Date: Thu, 04 Oct 2007 05:00:43 GMT
Content-Type: text/plain
Expires: Thu, 04 Oct 2007 05:00:43 GMT
Last-Modified: Thu, 04 Oct 2007 05:00:43 GMT
X-Cache: MISS from cache2-server
X-Cache-Lookup: MISS from cache2-server:3128
Via: 1.0 cache2-server:3128 (squid)
Proxy-Connection: close

Squid Object Cache: Version 2.6.STABLE14
Start Time: Fri, 31 Aug 2007 10:24:34 GMT
Current Time:   Thu, 04 Oct 2007 05:00:43 GMT
Connection information for squid:
Number of clients accessing cache:  4168
Number of HTTP requests received:   173803166
Number of ICP messages received:1090974817
Number of ICP messages sent:1095742664
Number of queued ICP replies:   9
Request failure ratio:   0.00
Average HTTP requests per minute since start:   3573.5
Average ICP messages per minute since start:-43347.4
Select loop called: -1251324801 times, -2.332 ms avg
Cache information for squid:
Request Hit Ratios: 5min: 50.6%, 60min: 50.2%
Byte Hit Ratios:5min: 27.6%, 60min: 29.1%
Request Memory Hit Ratios:  5min: 0.0%, 60min: 0.0%
Request Disk Hit Ratios:5min: 74.3%, 60min: 74.7%
Storage Swap size:  11074963 KB
Storage Mem size:   124912 KB
Mean Object Size:   9.27 KB
Requests given to unlinkd:  0
Median Service Times (seconds)  5 min60 min:
HTTP Requests (All):   0.04047  0.10281
Cache Misses:  1.46131  1.46131
Cache Hits:0.00091  0.00091
Near Hits: 1.17732  1.17732
Not-Modified Replies:  0.00091  0.00091
DNS Lookups:   0.06083  0.06364
ICP Queries:   0.00102  0.00108
Resource usage for squid:
UP Time:2918169.381 seconds
CPU Time:   325875.751 seconds
CPU Usage:  11.17%
CPU Usage, 5 minute avg:23.26%
CPU Usage, 60 minute avg:   25.13%
Process Data Segment Size via sbrk(): 789776 KB
Maximum Resident Size: 637880 KB
Page faults with physical i/o: 871
Memory accounted for:
Total accounted:   439005 KB
memPoolAlloc calls: 2618284649
memPoolFree calls: 2613332187
File descriptor usage for squid:
Maximum number of file descriptors:   8192
Largest file desc currently in use:   1969
Number of file desc currently in use: 1583
Files queued for open:   0
Available number of file descriptors: 6609
Reserved number of file descriptors:   100
Store Disk files open:   0
IO loop method: kqueue
Internal Data Structures:
1195109 StoreEntries
   741 StoreEntries with MemObjects
40 Hot Object Cache Items
1194406 on-disk objects



The reason there is high number of page faults is due to 2 long outages we had 
last month!.

I am also a little puzzled by the negative values of the Select loop called!

- ---

root# squidclient mgr:storedir

HTTP/1.0 200 OK
Server: squid
Date: Thu, 04 Oct 2007 05:07:02 GMT
Content-Type: text/plain
Expires: Thu, 04 Oct 2007 05:07:02 GMT
Last-Modified: Thu, 04 Oct 2007 05:07:02 GMT
X-Cache: MISS from cache2-server
X-Cache-Lookup: MISS from cache2-server:3128
Via: 1.0 cache2-server:3128 (squid)
Proxy-Connection: close

Store Directory Statistics:
Store Entries  : 1195347
Maximum Swap Size  : 12582912 KB
Current Store Swap Size: 11073264 KB
Current Capacity   : 88% used, 12% free

Store Directory #0 (coss): /cache1/squid/coss
FS Block Size 1024 Bytes

Maximum Size: 6291456 KB
Current Size: 5536468 KB
Percent Used: 88.00%
Current load metric: 0 / 1000
Number of object collisions: 2
Flags:
Pending Relocations: 0
Stripe: 1180, lockcount: 0, numobjects 40, flags: 
NOTFULL,NOTWRITING,NOTWRITTEN,DISK
Stripe: 1, lockcount: 4, numobjects 204, flags: 
NOTFULL,NOTWRITING,NOTWRITTEN,MEMONLY
Stripe: 1178, lockcount: 1, numobjects 124, flags: 
FULL,NOTWRITING,NOTWRITTEN,DISK