why udp recv slowly

[tianbinraindrop]

My openvms's version is 7.3-1.I have a multithread program to receive udp data.I find my program will lost some data when one computer sends 100 frames/second to my server.My server is ds25,and has a 1000M network card.Who can tell me how to fix this problem? Thank you

[Karl Rohwedder]

1st advice would be to read the tuning manual at http://h71000.www7.hp.com/doc/732final/documentation/pdf/aa-rn1vb-te.pdf

regards Kalle

[Wim Van den Wyngaert]

If you don't like reading, try increasing the buffers with ucx set prot udp/quo.

Make sure that the receiving process is not a low priority process.

Wim

[tianbinraindrop]

Thank you very much.I want to know what's mean of "ucx set pro/quo"? Wheater use qio is better than use socket?How much receiver buffer is best?

[Ian Miller.]

A bit more information about
"ucx set prot udp/quo"

Display current values
$ TCPIP SHOW PROTOCOL UDP

$ TCPIP SET PROTOCOL UDP/QUOTA=REC:x

To increase receive quota to x

[Wim Van den Wyngaert]

Simply start with the receive value you have (default is 9K) and double it, test performance, double it, test until the loss of packets is acceptable or until you notice that it doesn't help.

It may also be a question of quotas. Check if your process is not bouncing with certain limits (sh proc/quo or use ana/sys).

Or do wath Karl instructed.

Wim

[tianbinraindrop]

Thank you.I will try!
I want to know whether the efficiency of QIO is better than standard socket?By the way,I want to know how to implement semaphore in openvms 7.3-1?

[Uwe Zessin]

Hm. You do understand that UDP is a datagramm service with NO delivery guarantee, whatever you do to try to tune your machine?

If you need a guarateed delivery I am afraid you have to switch to another mechanism or develop one on your own.

[tianbinraindrop]

Yes,I know UDP without delivery guarantee,but my network card is 1000M,and I am sure this send rate is not fast,so I want to tune my machine to receive all udp data.

[Ian Miller.]

"I want to know whether the efficiency of QIO is better than standard socket?"

I don't think there will be much difference. sockets are layered on QIO

QIO allows asyncronous operation - sockets don't (without doing threads etc)

[Antoniov.]

If you have multithread program you could use socket interface so your software is more portable. QIO is not quicker than socket interface.

Antonio Vigliotti

[Wim Van den Wyngaert]

100 frames per second doesn't even generate 0.2 MB per second. I would say that your program isn't following (thus the frames are received and the receive buffer is full and frames are lost) or may be the router in between isn't following (and he is dropping the fragments).

Post the output of ucx sho prot
for further analyzing.

Wim