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

297 votes
Vote
Sign in
(thinking…)
Password icon
Signed in as (Sign out)
You have left! (?) (thinking…)
Tomasz Wisniewski shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

21 comments

Sign in
(thinking…)
Password icon
Signed in as (Sign out)
Submitting...
  • Simon commented  ·   ·  Flag as inappropriate

    Can't believe this is still "under review"... This resource juste takes forever to spin up...

  • Ricardo Costa commented  ·   ·  Flag as inappropriate

    4 years is not enough time to fix this issue, Microsoft likes to take their time to fix issues, analyze the problem, they can't rush things cause customers can wait, and then on a Sunday morning, when no one cares any longer about the issue, because something better came along and redis is outdated, bam that's when they will fix it, props to Microsoft for teaching me a great business model

  • 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?

← Previous 1

Feedback and Knowledge Base