Hi
I have a development prototype with Vendr and am using an azure sql server database (the Basic plan) and Umbraco 9.
I am doing simple stuff like creating an order, adding properties and saving it. However the vendr calls to SaveOrder are taking over 1 second which seems very high considering I don't have many orders in the database and no load at all.
Any thoughts? Its a bit of a show stopper in terms of using Vendr which is a shame as it seems very good.
Hi again
Success! This is a bit embarrassing but I had set up my app service in the UK and my database in the US (as it wouldn't let me use the UK West at the time, but managed to use UK South). I'd forgotten about this, but the rest of umbraco was working reasonably quickly.
I also added a few indexes on some of the order tables on orderid which made a small difference (maybe 0.25s). The main improvement was the DB location not surprisingly.
Down to under 300ms now.
Thanks for your help,
Sue
Vendr: Are there any know issues with Vendr and SQL Azure?
Hi I have a development prototype with Vendr and am using an azure sql server database (the Basic plan) and Umbraco 9. I am doing simple stuff like creating an order, adding properties and saving it. However the vendr calls to SaveOrder are taking over 1 second which seems very high considering I don't have many orders in the database and no load at all. Any thoughts? Its a bit of a show stopper in terms of using Vendr which is a shame as it seems very good.
Hi Sue,
We have a number of customers using Azure without issues so it should definitely work
Can I ask what Azure App instance / SQL DB sizes are you using?
Matt
Hi again Success! This is a bit embarrassing but I had set up my app service in the UK and my database in the US (as it wouldn't let me use the UK West at the time, but managed to use UK South). I'd forgotten about this, but the rest of umbraco was working reasonably quickly. I also added a few indexes on some of the order tables on orderid which made a small difference (maybe 0.25s). The main improvement was the DB location not surprisingly. Down to under 300ms now. Thanks for your help, Sue
Fantastic 🎉
Glad you were able to find the solution 👍
Matt
is working on a reply...