I don't have the exact number, however I can say this. When using hyperterminal and probing the pin with a scope the transition from low to high is instant. But when using LV, the transition has a delay which is visible to the eye. One can qualitatively judge that the transition in hyperterminal is quicker than LV.
Is this the VI I gave you to demonstrate one method of reading a variable number of bytes? If all you're experiencing is a delay on the writes, eliminate the configure serial port on every iteration. It only needs to be done once of the very beginning of a program. This example also needs a little cleanup to handle the case when nothing is returned by the instrument and you get a timeout.
This is the example you gave me. The config vi for the serial interface is only don't at the beginning of the program. It is set properly and runs nice. However their is a delay as I mentioned between hyperterminal and LV. What do you mean by cleanup?
The tick count function simply takes a reading from a system clock. In this program, it looks like these functions are being used to compare the time between different iterations of the loop that is waiting to see if bytes are at the port. If the difference between the tick count inside the while loop and the tick count that executes before the loop begins exceeds the timeout input, then the loop will stop.
In order to see more of why this program is running more slowly than hyperterminal, you could use the VI Profile option if you have the Professional edition of LabVIEW. Simply go to Tools, then Advanced..., and then select VI Profile. This allows you to see how much time was spent in each part of your code. If you do not have the Pro edition, then you may be able to do a makeshift version of the same functionality by using the tick count function. You can place the tick count function different places in your code, and compare the times between certain steps. However, this might affect the speed of execution of the code, so it is not the best way to do this.
The Tick Clock simply returns the value of the millisecond timer. In other words it is just counts in milliseconds. It is compared to an initial Tick Clock value because the Tick Clock will not necessarily start counting at 0.
As far as the delay you are experiencing, have you tried performing a loopback test with this VI? I didn't see any noticable delay when I tried it with loopback test.