P
Peter Judge
Guest
Good news/bad news. Bad first: there's a bug in the code that causes the caller to wait for the socket to time out instead of being closed when the payload is completely received. Good next: I have a fix mostly complete; if you could log a bug, then it'll be formally tracked. -- peter From: bronco [mailto:bounce-bfvo@community.progress.com] Sent: Tuesday, 23 December, 2014 11:48 To: TU.OE.Development@community.progress.com Subject: [Technical Users - OE Development] OpenEdge.Net library performance OpenEdge.Net library performance Thread created by bronco While playing around with 11.5 I noticed the following: A simple Ping implemented via REST (PAS) now takes 15ms (vs +/- 40ms in 11.4). -60%, great! The time is measured via Postman, a Google Chrome App. Now on the subject of this post: when I try to consume this REST service from the 4GL via the OpenEdge.Net library it takes about 2500 to 3000ms. The code: httpRequest = RequestBuilder:Get(" http://localhost:9080/testapp1/rest/testapp1/system/ping "):Request. httpRequest:AddHeader("request-id", "abc12345"). t1 = mtime. httpResponse = HttpClient:Instance():Execute(httpRequest). t2 = mtime. Now there's obviously some Json parsing as well, but 2,5 seconds it is still quite a long time, especially when such a call is done on the AppServer where time is measured in milliseconds than in seconds. Does anyone have a suggestion how to improve on this? I've been looking into 3rd party solution (dll, so) but these somehow add considerable complexity to the overall solution. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...