Kind of off topic, but can someone from google explain the Quota
implications of the Channel API.
I see above there is considerable CPU associated with creating the
socket. Can you provide more details around if we will be paying for
all the requests the JS api makes to keep the socket open?
Thanks Moishe.
Channel set-up time (the time between when you call
goog.appengine.Channel.open and when your socket.onopen callback gets
called) can be longer, sometimes up to 10 seconds or so.
This very likely explains the behaviour I was seeing.
j
On Dec 5, 12:57 am, Moishe
The channel api cost a lot of cpu.
*
xmpp.CreateChannel* real=3ms *api=2770ms*
Happy coding ! [?]
Tom Wu
2010/12/4 风笑雪 kea...@gmail.com
In my opinion, it's super fast that I couldn't feel the latency.
--
keakon
--
You received this message because you are subscribed to the
I also noticed that, but the response time is only about 10ms:
/get_token 200 11ms 2770cpu_ms 2770api_cpu_ms 0kb Mozilla/5.0 (Windows; U;
Windows NT 5.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko)
Chrome/7.0.517.41 Safari/534.7 ChromePlus/1.5.0.0,gzip(gfe)
114.92.72.48 - keakon
Latency should be generally significantly less than 500ms (that's not
a guarantee, but it's what I've been seeing in my end-to-end tests).
Channel set-up time (the time between when you call
goog.appengine.Channel.open and when your socket.onopen callback gets
called) can be longer, sometimes up
It could be that the latency on the messages is high and I'm just not
patient enough.
So, maybe my next question is, what kind of latency can we expect on
Channel API messages?
j
On Dec 3, 2:59 pm, Jason Collins jason.a.coll...@gmail.com wrote:
Doing some work today with the Channel API (using
In my opinion, it's super fast that I couldn't feel the latency.
--
keakon
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from this group, send
