READ_ANSW_TIMEOUT

change to 5mins

Install gigabase dB. working better that berk. dB.

oops seems to working pretty good and keeping tracks with threads.

normal removing cache cause a hit ratio of 3-9% for about a week.

>From start, hit ratio when from 9% to 25% with a couple of hours. chech
average hit below.

Could this be because of my new config(part of)?

mem_max  64m
lo_mark  18m
start_red 900
refuse_at 920
default-expire-value    20
ftp-expire-value 20
max-expire-value        30
last-modified-factor 5
default-expire-interval 24
disk-low-free 0
disk-ok-free 0
force_http11
always_check_freshness
force_completion 65
maxresident 32m
insert_x_forwarded_for yes
insert_via  yes
fetch_with_client_speed no

acl VIRUS urlregex system32
acl VIRUS1 urlregex root.exe
acl VIRUS2 urlregex default.ida

acl_deny VIRUS ALL
acl_deny VIRUS1 ALL
acl_deny VIRUS2 ALL

module gigabase_db {

       dbhome  /usr/local/oops/DB
       dbname  dburl
       db_cache_mem    64m

}

By giving "db_cache_mem" more cause this? That was the only thing I change
after setting up oops again!

      General Info
      Version  1.5.22
      Uptime  181356sec, (2day(s), 2hour(s), 22min(s))
      Last update  Sun Mar 10 18:09:59 2002
      Clients  132 (max: 483)
      HTTP requests  1636527
      ICP requests  0
      Total hits  546984
      Thread pool  192 ready to serve (out of 1000 max)
      Curr.req.rate  9.98 req/sec (max: 18.90)
      Tot.req.rate  9.02 req/sec
      Curr.hit.rate  35.23 %
      Tot.hit.rate  33.42 %
      Curr.icp.rate  0.00 req/sec (max: 0.00)
      Total usage  151820ms
      Delta usage  0ms
      Delta time  60000ms
      Curr. CPU  0.00 % (0.00s+0.00u)
      Aver. CPU  0.08 % (0.00s+0.08u)
      Storages
      Disks msg  Cleanup finished
      Storage  /cache1/oops_storage
      Size  7910.00 MB
      Free blks  1740155 blks (6797.48Mb) 85.94 %
      State  READY
      Fileno  10
      Storage  /cache2/oops_storage
      Size  7910.00 MB
      Free blks  1749846 blks (6835.34Mb) 86.41 %
      State  READY
      Fileno  33
      Storage  /usr/local/oops/storages/oops_storage
      Size  3250.00 MB
      Free blks  550524 blks (2150.48Mb) 66.17 %
      State  READY
      Fileno  34
      Module  Type
      DummyLog  Dummy logging module (Log recording)
      CustomLog  Customized access log. (Log recording)
      oopsctl  Oops controlling module (Independent port listener)
      wccp2  Web Cache Coordination Protocol v2.0 (Independent port
listener)
      accel  WWW-accelerator (URL redirector)
      fastredir  Fast Substring URL Redirector (URL redirector)
      redir  Regex URL Redirector (URL redirector)
      transparent  Transparent proxy (URL redirector)
      lang  National languages handling module (Output handling)
      err  Error reporting module (Error reporting)
      passwd_file  Auth using passwd file (Auhtentication)
      pam  Auth using PAM (Auhtentication)
      passwd_mysql  Auth using mySQL %s (Auhtentication)
      passwd_pgsql  Auth using PostgreSQL %s.%s.%s (Auhtentication)
      vary  Processing 'Vary:' header (Document headers check)
      berkeley_db  BerkeleyDB %d.%d.%d API (DB Interface)
      gigabase_db  GigaBASE %d.%d API (DB Interface)
      icp peers


Tonight and tomorrow night will test the cache since an expected 24+ req/sec
will be expected.

I have even seen 40+ req/sec in the oops.cfg.

Thank you very much.

Best regards,

Edward Millington. BSc, Network+
Systems Administrator
Cariaccess Communications Ltd.
Palm Plaza
Wildey
St. Michael
Barbados
1-246-430-7435
Fax : 1-246-431-0170
[EMAIL PROTECTED]
www.cariaccess.com


----- Original Message -----
From: "Igor Khasilev" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, March 08, 2002 1:03 PM
Subject: Re: [OOPS] increasing the number of threads on linux


> On Fri, 8 Mar 2002, Edward Millington wrote:
>
> > Is that in the config? READ_ANSW_TIMEOUT
>
> in the oops.h
>
> >
> > Set it yesterday:-
> > start_red 900
> > refuse_at 920
> >
> > start_red was at 950 when it happened yesterday.
> >
> >
> > > You can try to change READ_ANSW_TIMEOUT from 10 minutes to something
> > lower.
> > > But, if I understand you correctly, you should set start_red and
refuse_at
> > > to some values lower than 1000
> > >
> >
> >
> >
> > =====================================================================
> > If you would like to unsubscribe from this list send message to
> > [EMAIL PROTECTED] with "unsubscribe oops-eng" in message body.
> > Archive is accessible on http://lists.paco.net/oops-eng/
> >
>
> Igor Khasilev                   |
> PACO Links, igor at paco dot net  |
>
> =====================================================================
> If you would like to unsubscribe from this list send message to
> [EMAIL PROTECTED] with "unsubscribe oops-eng" in message body.
> Archive is accessible on http://lists.paco.net/oops-eng/
>


=====================================================================
If you would like to unsubscribe from this list send message to
[EMAIL PROTECTED] with "unsubscribe oops-eng" in message body.
Archive is accessible on http://lists.paco.net/oops-eng/

Дати відповідь електронним листом