HTTPS POST performance
-
wrote on 29 Sept 2018, 23:26 last edited by
I've an app that send HTTPS POST requests to a known address with known datas. I found out that first request take more time than the others!
So now I fire 1 request at startup so within 1 minute I can send faster all other requests. Right now it takes 1000ms +-50ms to get a response, I'd like to know if I can optimize my code even more to get a better result!
Searching on google I found this: http://wiki.qt.io/QtNetwork_performance -
I've an app that send HTTPS POST requests to a known address with known datas. I found out that first request take more time than the others!
So now I fire 1 request at startup so within 1 minute I can send faster all other requests. Right now it takes 1000ms +-50ms to get a response, I'd like to know if I can optimize my code even more to get a better result!
Searching on google I found this: http://wiki.qt.io/QtNetwork_performance@wrekler
to what server do you send this request?Searching on google I found this: http://wiki.qt.io/QtNetwork_performance
and did you try any of the suggestions yet?
-
@wrekler
to what server do you send this request?Searching on google I found this: http://wiki.qt.io/QtNetwork_performance
and did you try any of the suggestions yet?
wrote on 30 Sept 2018, 19:23 last edited byto what server do you send this request?
How relevant is knowing the server?
and did you try any of the suggestions yet?
No, I really don't know how implement some of them because, as I see, all links point to old BUG reports.
-
Hi and welcome to devnet,
@wrekler said in HTTPS POST performance:
How relevant is knowing the server?
It is relevant because:
- It might be sleeping if for example it's an heroku free tier that hasn't been used for some times. Therefore the first query will have to wait for the server to awaken thus it will be longer.
- It might require authentication which takes some time on first query to setup and allow to process.
- It might need to query some slow to start resource to answer your question
- etc.
-
Hi and welcome to devnet,
@wrekler said in HTTPS POST performance:
How relevant is knowing the server?
It is relevant because:
- It might be sleeping if for example it's an heroku free tier that hasn't been used for some times. Therefore the first query will have to wait for the server to awaken thus it will be longer.
- It might require authentication which takes some time on first query to setup and allow to process.
- It might need to query some slow to start resource to answer your question
- etc.
wrote on 30 Sept 2018, 20:55 last edited by wrekler@SGaist said in HTTPS POST performance:
Hi and welcome to devnet,
@wrekler said in HTTPS POST performance:
How relevant is knowing the server?
It is relevant because:
- It might be sleeping if for example it's an heroku free tier that hasn't been used for some times. Therefore the first query will have to wait for the server to awaken thus it will be longer.
- It might require authentication which takes some time on first query to setup and allow to process.
- It might need to query some slow to start resource to answer your question
- etc.
Oh, I see. Well it is not a my server, it is a thirdy party server, so I can't answer to all that question. All I know is:
- It is hosted on akamai.com
- Acqtually it require some authentication data that I give with POST data
So I think I can't optimize requests server side, all can I do is caching DNS/TCP/SSL requests but I don't know if Qt 5.11.2 actually implements all that suggestions
2/5