Search Unity

Very poor performance with property of UnityWebRequest.url

Discussion in 'Scripting' started by iyc, May 6, 2016.

  1. iyc

    iyc

    Joined:
    Jul 29, 2014
    Posts:
    11
    This is not a bug, but I found that property setter of UnityWebRequest.url has a very poor performance. It will takes about 0.6ms on editor (OSX), and even more with smartphones. This is because there are internal checks for values, but I don't need this slow checks and I want to set URL directly. Since there are no way to do this, I'm using InternalSetUrl with reflection.

    Are there any improvements planning for this issue?
     
  2. BananaAcid

    BananaAcid

    Joined:
    Aug 9, 2017
    Posts:
    2
    this is still the case. On Android Galaxy S6 a simple request, local network, http, took 2 min. I encountered it before in .NET 2.0 -> a Proxy-Lag-Bug. Not disabling any proxy functionality on a request made it take forever. A working fix for Unity is https://stackoverflow.com/a/43678419/1644202 . Implementing an option to disable any proxy lookups on `UnityEngine.Networking.UnityWebRequest()` would fix this.