Winsock Performance CETK Test

I tested 1007 UDP Send Throughputand 1008 UDP Send Packet Loss in the Winsock
Performance CETK Test use wince600 cetk tools.I found the two item is always
fail.
The fail log is as following:
ReceiveServiceReponse() timed-out
Communication between server and client failed; terminating test
But If we use wince500 cetk tool to test Winsock Performance .The test case
can pass.
So I start study the differents of the wince500 test souce between wince500
test souce.The Winsock test case setup two socket ,One for control socket use
TCP ,another for work that can be use TCP or UDP.
We found in wince500 ,the work socket setup use SO_KEEPALIVE mode.Wince600
is not setup a SO_KEEPALIVE mode.Who please can give me some comments?

Hi,

I have same problem.

I can pass test case 1007 in WinCE5.0, but it has some problems here.
The RecvRate is not correct .
like this...
Send Packet Bytes Sent Send Rate Recv Rate CPU Util Packets Recvd
(Bytes) (Bytes) (Kbps) (Kbps) (%)
(%) (#recv/#sent)
----------- ----------- ----------- ----------- -------- ------
-------------
256 1280000 5311.20 10219520.00 31.54 99.80 4990/5000
256 1280000 5311.20 10219520.00 31.54 99.80 4990/5000

I check out the source code.
the Recv Rate is calculated in this way:
(double)dwPacketsRecvd * dwRecvPacketSize * 8. / (double)dwRecvTime);

I found that the dwRecvTime=1 when packets dropped.
So the value is 4990*256*8/1=10219520.00

We can retrieve test response from server (you can check out procedure
"ReceiveTestResponse")
but the response seems not correctly when packets dropped.
The Recv time is 0 in the response, and it will be corrected to 1as
mentioned before.
So the value is 4990*256*8/1=10219520.00

Why should the Recv time be 0 when packets dropped?

Best regards
Sean


"make" wrote:

> I tested 1007 UDP Send Throughputand 1008 UDP Send Packet Loss in the Winsock
> Performance CETK Test use wince600 cetk tools.I found the two item is always
> fail.
> The fail log is as following:
> ReceiveServiceReponse() timed-out
> Communication between server and client failed; terminating test
> But If we use wince500 cetk tool to test Winsock Performance .The test case
> can pass.
> So I start study the differents of the wince500 test souce between wince500
> test souce.The Winsock test case setup two socket ,One for control socket use
> TCP ,another for work that can be use TCP or UDP.
> We found in wince500 ,the work socket setup use SO_KEEPALIVE mode.Wince600
> is not setup a SO_KEEPALIVE mode.Who please can give me some comments?
>

Hello,

I get same problem with CE 6.0 R2.
Did you resolve this issue?

Thanks,
Woojung

"make" wrote:

> I tested 1007 UDP Send Throughputand 1008 UDP Send Packet Loss in the Winsock
> Performance CETK Test use wince600 cetk tools.I found the two item is always
> fail.
> The fail log is as following:
> ReceiveServiceReponse() timed-out
> Communication between server and client failed; terminating test
> But If we use wince500 cetk tool to test Winsock Performance .The test case
> can pass.
> So I start study the differents of the wince500 test souce between wince500
> test souce.The Winsock test case setup two socket ,One for control socket use
> TCP ,another for work that can be use TCP or UDP.
> We found in wince500 ,the work socket setup use SO_KEEPALIVE mode.Wince600
> is not setup a SO_KEEPALIVE mode.Who please can give me some comments?
>