RE: socket problem

Hi all,

My socket server is having this weird problem at one of our customer sites.
Whenever the program gets to the select() the CPU% cranks up to 15%-18%.
What I don't understand is why it only happens on this one 400, other
customers typically run around 1%-2%.

The program sends a request for data to the partner pgm and then does
select().  If FD_SET indicates there is data available the program does a
read().  The program loops on the select() & read() until an 'end or record'
string is encountered at which point the program spits the data out to a
dtaq and then sends the next request for data to the partner program.  The
parnter program doesn't push data at the RPG socket pgm until a record is
requested... the RPG polls the partner.

So why does select() suck up so much CPU and how can it be fixed?  Any
ideas?


Tom