Tuning the Scheduler
- From: "Darol" <darol.klawetter@xxxxxxxxxx>
- Date: 17 Apr 2006 08:23:40 -0700
I have a Linux app, let's call it App1, that uses a TCP/IP socket to
communicate with the socket of another app, App2. The problem is that
the App2's receive socket buffer eventually overflows because it cannot
keep up with the rate at which App1 is sending TCP/IP messages. When I
view the CPU utilization using Top, I notice that the CPU is idle about
75% of the time. Because of this large amount of idle time, It seems to
me that there is plenty of CPU power to prevent the receive buffer
overflow if the scheduler can somehow be make aware of the receive
buffer state (say via some kind of high watermark indication).
Is there a way to tune the scheduler so that it gives App2 the time it
needs to prevent buffer overflow? BTW, App2 is not waiting on anything
which would prevent it from being run as it's receive buffer begins to
fill.
Thanks,
Darol
.
- Follow-Ups:
- Re: Tuning the Scheduler
- From: Robert Redelmeier
- Re: Tuning the Scheduler
- From: Darol
- Re: Tuning the Scheduler
- From: Lew Pitcher
- Re: Tuning the Scheduler
- Prev by Date: Re: general archiving - tar and ar
- Next by Date: Re: Tuning the Scheduler
- Previous by thread: general archiving - tar and ar
- Next by thread: Re: Tuning the Scheduler
- Index(es):
Relevant Pages
|