Hi,
I don’t know what would cause this, to be honest, but some things which might help your debugging:
You can provide a QNetworkManager to the QML engine, which will be used for all network communication (including remote imports, remote image fetches, and xmlhttprequests). The API is a bit strange, IIRC, as you actually pass a pointer to a factory function, I think. If your factory instantiates an instance of a custom subclass of QNAM, you can override the performRequest() virtual function (or something, I can’t remember). Thus, you can get timings of when the actual network request is performed, compared to when it finishes.
The issue could be related to QNAM / QtBearer trying to figure out which route to use for the requests, or something, for example.
You could also try running the application under QtCreator with the QML analyzer enabled, to try to see what’s going on, but I expect it’s not anything in QML itself which is taking up the time (although I may be wrong).
Cheers,
Chris.
↧