From: "Tushar Gupta" <tushar@surevin.net>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Bandwidth Restrictions in Linux
Date: Mon, 27 Jan 2003 14:52:27 +0000 [thread overview]
Message-ID: <marc-lartc-104367874616055@msgid-missing> (raw)
In-Reply-To: <marc-lartc-104335929011822@msgid-missing>
Hi,
We are using squid for caching, with SCSI disk and 512 MB RAM. The
cache_mem setting in squid.conf is 64 MB. After running for several
hours total free RAM (as seen by top command) reduces to few kilobytes
and server response time increases (CPU idle cycles also go to zero),
and we need to reboot the server. Though as percentage of total CPU
usage squid is usually taking around 15-30%CPU and percentage of RAM as
12-15%MEM . After rebooting the server would again run fine for several
hours say half a day, and then RAM would gradually get consumed again.
Any suggestions are welcome.
Thanks
Tushar
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl]
On Behalf Of Mathieu Deziel
Sent: Monday, January 27, 2003 7:33 PM
To: lartc@mailman.ds9a.nl
Cc: robert.kryczalo@iscnet.pl; rravetti@itc.com.ar
Subject: RE: [LARTC] Bandwidth Restrictions in Linux
>
> Hello
> > We are ISP and we give Internet Wireless Outdoor Service . The
> > Base Station
> > works in 802.11b and it is connected with a Linux Mandrake Server
> > that make
> > NAT.
> 802.11b devices are by design experiencing "hidden node" effect.
"Hidden node" problem can be avoided by the use of RTS-CTS (request to
send, clear to
send). RTS-CTS are optional but can be enabled. You can also specify a
threshold in
the size of the packet under which RTS-CTS will not be used, in which
case the hidden
node problem might occur for those packets. RTS-CTS will solve the
hidden node
problem, but will consume BW.
Mathieu.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-01-27 14:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-23 21:59 [LARTC] Bandwidth Restrictions in Linux Intercom - Roberto Ravetti
2003-01-24 9:08 ` ISC Robert Kryczalo
2003-01-24 15:16 ` Intercom - Roberto Ravetti
2003-01-24 18:57 ` ISC Robert Kryczalo
2003-01-25 8:43 ` ISC Robert Kryczalo
2003-01-27 5:38 ` S Mohan
2003-01-27 14:03 ` Mathieu Deziel
2003-01-27 14:52 ` Tushar Gupta [this message]
2003-01-27 15:15 ` Debreczeni Peter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-104367874616055@msgid-missing \
--to=tushar@surevin.net \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.