How can we improve Azure Cache?

Work on creation time of Redis Cache

The time of creating a Redis Cache is to long. It should be improved

229 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Tomasz Wisniewski shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    18 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • John commented  ·   ·  Flag as inappropriate

        The azure redis cache is extremely slow to create. oh my god!

      • Matt Byrne commented  ·   ·  Flag as inappropriate

        Ridiculous that this is still an issue. Infrastructure provisioning that would otherwise take about 3 minutes end up taking 20+ while they wait for Redis.

      • Sébastien sougnez commented  ·   ·  Flag as inappropriate

        How long will this issue be ignored ?!

        20 minutes to create a redis cache while creating two new web app with SQL server and database take around 3 min.

        Microsoft really needs to stop ignoring this.

      • Richard commented  ·   ·  Flag as inappropriate

        I'm also interested in the status. We use Redis Cache at various clients, and the deployment is incredibly slow. Especially compared to many other Azure services. This needs to be improved.

      • Archon Andrew commented  ·   ·  Flag as inappropriate

        Just want to echo sentiments here, Redis deployment is easily the slowest part of our infra step.

      • Joz Ahmed commented  ·   ·  Flag as inappropriate

        Has there been any updates on this?
        It's taken 20 mins to create and destroy redis cache.
        This issue has been open since February 2015.

      • Mardy Dacasin commented  ·   ·  Flag as inappropriate

        Any update from this? I am experiencing this issues. It tooks long minutes for the provisioning.

      • Matthew Shooshtari commented  ·   ·  Flag as inappropriate

        Redis Cache is the long pole in our deployment. If this can be shortened our application deployment time could be cut by 3/4.

      • Sam commented  ·   ·  Flag as inappropriate

        We have our infrastructure scripted. Theres quite a bit of it, it usually takes 3.5 minutes to create followed by 20 minutes of waiting for redis to provision

      • Lachlan White commented  ·   ·  Flag as inappropriate

        Hi Team, Can this also please include the time it takes to delete the Redis Cache.

        Both of these operations take around 20-40 minutes at the moment

      • Michal Koziorowski commented  ·   ·  Flag as inappropriate

        Hi.
        Any news about that item?

        We are doing at least 20 - 50 deployments a day, each containing premium redis instance. Because everything waits for redis, deployment takes ages. Our VMs start in about 3 minutes, and we often wait for redis about 25+ minutes.

      • John Leidegren commented  ·   ·  Flag as inappropriate

        In the meantime can anyone comment on why it takes 30 minutes? It's bizarre and incredibly annoying. In the event of a disaster, we have to wait 30 minutes just because we have a Redis cache in our deployment, makes you think twice about even having it there. Should we just not use Redis?

      • Graham Ambrose commented  ·   ·  Flag as inappropriate

        Just to give some context to how bad create times are these are timings from two arm template deployments I just ran.

        Time to create a Sql server and provision a database 1 min 10 secs. Time to create a Redis cluster 14 mins 44 secs.

      Feedback and Knowledge Base