ok.

I just wanted to b clear on the db one.

as I stated before, I am trying to account an increase in hit ratio and
response time after setting up oops.

Since changing "READ_ANSW_TIMEOUT" to 5mins threads are tracking properly
with client.

Before clients would have spend 2-3mins at 200 after reaching a peak at
450., but thread would decrease slowly over time to some value near the
client usage.

I took a look at an email you sent me last year on a working machine stats
and saw those high value of clients and req/sec.

So I do know, I should be able to get more out of oops.

Again, 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: Monday, March 11, 2002 2:44 AM
Subject: Re: [OOPS] memory usage


> On Sun, 10 Mar 2002, Edward Millington wrote:
>
> > Hi there!
> >
> > Can some one please tell me what are the usages of:
> >
> > mem_max  64m
>
> If total amount of documents in memory reach mem_max, then we start drop
> documents without save to disk.
>
> > lo_mark  18m
>
> When total amount of documents in memory reach lo_mark we start swpa thm
out
> to disk. this process swap out as much documents as we need to return back
> to lo_mark (and a bit more, so we will no need to swap them out too
> frequently)
>
> > db_cache_mem    in:
>
> This paramenter for internal database library usage - it is size of
internal
> cache where library keep recently used pages.
>
> >                                 module gigabase_db {
> >
> >                                dbhome  /usr/local/oops/DB
> >                                dbname  dburl
> >                                db_cache_mem    64m
> >
> >                                 }
> >
> > What results would occur if those values would have been increase in
> > relation to others especially "db_cache_mem"?
>
> if you increase db_cache_mem you will probably see less(and maybe bursty)
> disk io with database.
>
> >
> >
> > 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
> >
> >
> >
>
> 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/

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