Clever Geek Handbook

Performance Impact of Calling CreateIfNotExistsAsync () on Azure Queue

Should I call CreateIfNotExistsAsync()

before every read / write to the Azure queue?

I know this results in a REST call, but is it doing any IO on the queue?

I am using the library .Net

for Azure Queue (if this information is important).

+3


source to share


1 answer


All this method does is try to create the queue and catch the AlreadyExists error, which you could just as easily replicate by catching a 404 while trying to access the queue. Some of these will affect performance.

More importantly, it increases your costs: From Understanding Windows Azure Storage Billing - Throughput, Transactions, and Capacity [MSDN]



We've seen applications that queue CreateIfNotExist [sic] before each message that is placed on that queue. This results in two separate storage requests for each message they want to queue when the create queue fails. Make sure you only create your containers, tables, and Blob queues early in life to avoid this additional transaction overhead.

+4


source






More articles:


All Articles