Created by: Anthony Palomba on 10-12-2010 07:01:42 PM I have been doing some testing with the TC4.0 and our C60 and am encountering some bad latency.
When we first setup the C60, it was running TC3.12 and it seemed to be pretty responsive to API commands. Now that we upgraded, I am getting long latencies when API sending commands.
MXP: 144 ms V1: 97 ms C90: 177 ms EX90: 81 ms C60: 1813 ms
But when I ping the C60, I get fast times…
Pinging 10.10.10.59 with 32 bytes of data: Reply from 10.10.10.59: bytes=32 time=2ms TTL=64 Reply from 10.10.10.59: bytes=32 time=8ms TTL=64 Reply from 10.10.10.59: bytes=32 time=3ms TTL=64 Reply from 10.10.10.59: bytes=32 time=1ms TTL=64
So it is not our network. It would seem that TC4.0 has bad HTTP response times now.
We use the API to do real time operations like dialing, camera control, composting, etc. The latency really degrades the usability of the API.
Result is the same with Snapshots turned on or off. Can someone please look in to this.
Thanks, Anthony
Subject: RE: Bad HTTP API performance on TC4.0 Replied by: Anthony Palomba on 13-12-2010 11:51:45 PM I have confirmed that downgrading from TC4.0 to TC3.1.2, latency goes from 1813 ms to 75 ms!
Subject: RE: Bad HTTP API performance on TC4.0 Replied by: David Bruun-Lie on 14-12-2010 11:22:20 AM Hi Anthony,
we are unfortunately aware of the performance issues on HTTP in TC 4.0. It was necessary to do some changes to the authentication mechanisms on HTTP due to new US government requirements. Unfortunately this caused a slowdown of the whole interface. We are working on improving the performance for coming software releases.
Regards, David
Subject: RE: Bad HTTP API performance on TC4.0 Replied by: Anthony Palomba on 03-01-2011 08:58:20 PM Hello David,
Thanks for the update. Now that the holidays have blown over, I was able to test the latest TC4 release...
It looks like the latency issue has been improved, but is still painfully slow to use. Especially if you are trying to do composting commands.
Can this issue please be looked at again. We use the API for real-time communication with the codec, the current latency makes it impossible to use beyond simple scenarios.
Will there be an update any time soon?
Thanks, Anthony
Subject: RE: Bad HTTP API performance on TC4.0 Replied by: Anthony Palomba on 10-01-2011 06:12:43 PM Can someone please respond to this. This is pretty serious... Is this issue going to be addressed any time soon?
Our product basically uses the API for real time control. In order to have our product work as it did with TC3, would take some considerably development effort to compensate for the current poor performance of the API.
It would be nice to have an idea as to when the API will be fixed so we do not have to waste valuable development time trying to address an issue that hopefully will be fixed.
Subject: RE: Bad HTTP API performance on TC4.0 Replied by: Johan Randby on 19-01-2011 04:04:03 PM Anthony, We are working on this issue, I can assure you that we also see it as a serious problem. However, at the moment I can not provide any estimate on when it is going to be fixed. I will update you early next week, as I will have more information by then.
Regards, Johan
Anthony Palomba:
Can someone please respond to this. This is pretty serious... Is this issue going to be addressed any time soon?
Our product basically uses the API for real time control. In order to have our product work as it did with TC3, would take some considerably development effort to compensate for the current poor performance of the API.
It would be nice to have an idea as to when the API will be fixed so we do not have to waste valuable development time trying to address an issue that hopefully will be fixed.
Subject: RE: Bad HTTP API performance on TC4.0 Replied by: Anthony Palomba on 28-01-2011 07:48:51 PM Hello Johan,
Thank you for your attention to this issue. We have been testing with various beta builds here and have been seeing improvements. In fact the latest beta build (tc41rc2) works great! API response time is now under 150 ms.
We really appreciate the development effort made to resolve this issue.
Is there a planned date for when the release candidate will be generally available?
Many thanks, Anthony
Subject: RE: Bad HTTP API performance on TC4.0 Replied by: Johan Randby on 31-01-2011 12:29:10 PM Anthony,
Great to hear that you are satisfied with the http api speed of tc41rc2! As always we can not give any guarantees regarding release dates, but it may look like next week is a good guess!
Best Regards,
Johan
Subject: RE: Bad HTTP API performance on TC4.0 Replied by: Johan Randby on 02-02-2011 05:09:03 PM
Anthony Palomba:
Hello Johan, In fact the latest beta build (tc41rc2) works great! API response time is now under 150 ms.
Anthony, I´m curios about how you measured this, and whether it was a POST or a GET?
BR, Johan
Subject: RE: Bad HTTP API performance on TC4.0 Replied by: Anthony Palomba on 02-02-2011 10:22:44 PM We are doing most of our development in .net, It provides a high resolution timer that allows me to take a reading before I send out the HTTP request, then I take a reading after the response comes back. I keep a running average of the round trip time of all API commnads. The requests we are sending are POSTs.
Subject: RE: Bad HTTP API performance on TC4.0 Replied by: Johan Randby on 03-02-2011 08:41:44 AM Thanks for your reply Anthony!
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
