Work on creation time of Redis Cache
The time of creating a Redis Cache is to long. It should be improved
Thank you for your feedback. This is on our backlog
Redis Cache in 2020 create in West Europe it will take approximate 35 to 40 minutes
Farukh Sharipov commented
West US still 5 years latter and I am waiting on my 27th minute for Azure Redis to be created..
Ryan Byrne commented
France Central, standard redis cache (C1) - Just under 40 mins to deploy via Terraform.
To echo everyone else this is really hampering deployment patterns.
Alexander Trauzzi commented
These start times are unreasonable. Move this service to linux and pass down some savings. I do not understand why you would run redis on Windows?!
Oskar Kirmis commented
Europe West, same. Even the smallest instance takes at least 30-45 minutes to spin up.
Ye Gu wrote:
"Azure Cache currently runs on Windows VM's and the creation time is largely determined by how fast the underlying VM's become available on-demand."
At least for Redis, it might be worth to consider alternatives for the underlying OS. And I don't see why this is "under review" 5 years later :(
UK south, it took 65 minutes to deploy redis......
Ye Gu commented
We understand that the Azure Cache creation time is long and that's been frustrating to you and us. Azure Cache currently runs on Windows VM's and the creation time is largely determined by how fast the underlying VM's become available on-demand. We hope that Windows server 2019 will help improve this situation. Otherwise we'll have to look at alternative VM types.
Has this even been investigated?
Even a workaround (e.g. if there are setting config values that makes a difference, or any API call for checking status beforehand) or explanation would be better than knowing it's on the backlog.
I would be surprised if you don't know more about why this is the case at this point, and it would be helpful if that information was the top MSFT post here. It's hard to go to internal clients with 'Microsoft are working on it for 4 years', even if that's a valid reason.
EDIT: 4 years, not 5. I can't count.
Darren Kattan commented
This is still a problem. Any updates?
+1, Australia East is slow as well. Affecting productivity here.
Agreed that this is ridiculously slow. This is my first time deploying this and i've been waiting over 55 minutes in US East.
Is this still on the backlog? Can't see any MS updates on this issue. Seems like everyone has the same issue that this is the longest deployment time of a pipeline. Have tried powershell, ARM template, manual and all of these are too long.
Mathieu Buisson commented
Deploying an Azure Redis Cache resource with Premium SKU takes more than an hour in North Europe location.
This is crippling our deployment automation capabilities.
Christian Bankester commented
It has now been more than 4 years that this item is in the backlog. I realize that this might be of relatively low priority compared with other problems in the Azure ecosystem, but surely 4 years is enough time for someone to take a look and give us a quick update.
Torgeir Hansen commented
I'm currently waiting for it to be created, about an hour spent waiting so far 😑
Patrick Truskowski commented
I upvoted this and don't understand why the provisioning is so slow. Attached a screenshot where it's taking 11+ minutes to deploy and still not finished.
Can't believe this is still "under review"... This resource juste takes forever to spin up...
Delete is still incredibly slow
Ricardo Costa commented
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
The azure redis cache is extremely slow to create. oh my god!