Hi Shawn,
I noticed your other post but have been busy at work (I only answer Q's in my spare time).
Check out the thread below for alot of talk about optimizing ethernet throughput.
There is something called the "Nagle algorithm" (sp?) that goes like this.
Ethenet packets are not nessesarily sent when you request. The are allowed to pile up until enough data available to make optimal use of the network. If the pile does not get big enough in a fixed amount of time, the TCP stack will time out and send the less than optimal packet.
This option can be shut off,
or
you can take this fact into concideration and make sure you are transmitting packets of optimum size.
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506
50000000800000007BE0000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0&USEARCHCONTEXT_INCLUDE_0=ben+ethernet&USEARCHCONTEXT_INCLUDE_S=0&UPostedFromTimeSearchArg_0=29&UPostedFromTimeSearchArg_1=3&UPostedFromTimeSearchArg_2=2001&UPostedFromTimeSearchArg_S=4&UPostedToTimeSearchArg_0=25&UPostedToTimeSearchArg_1=9&UPostedToTimeSearchArg_2=2004&UPostedToTimeSearchArg_S=4&USEARCHCONTEXT_TIER_0=2&USEARCHCONTEXT_TIER_S=0
RE:UDP
UDP does not guarentee that a packet will be delivered
or
that it will transmit packets in the order you send them.
I think of UDP as advertising or junk mail. You have to keep sending the same thing over and over if you want to get your message out.
Typical uses for UDP would be announcing a node is available to serve a printer.
I hope this helps,
Ben