Open Piedone opened 3 years ago
Hi @Piedone By default, Azurite cannot take full use of all CPU cores due to limitation of Node.js. That's the main bottoleneck. Recommendation is to do some performance testing based on your workload to see if Azurite can meet your requirement.
I see, thank you. This is what you're referring to by Node.js limitations?
Could you reply here, please?
Yes, for our emulator usage, NodeJs is Single threaded, and Azurite will process requests serially. Clustering will not improve the behavior, and we are using LokiJs for storage and cross platform support.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Not a bug but a question. Let me know if this is not the right place to ask.
Can you give some idea on how Azurite scales? The docs says that:
We'd like to use Azurite as the storage for an ASP.NET Core app when running UI tests on it, to see if it has any issues with storage once deployed to Azure and using Blob Storage. We're usually running dozens of concurrent tests at a given time up to the hardware limits of the machine (a VM with 16 vCPU cores, 64GB of RAM, SSD storage). Can we say that as long as the machine's hardware is not saturated Azurite will continue to serve requests or is there some inherent limitation?
Thank you!