There is a performance penalty when using auto-reloading. So keep in mind that you should not use it in production or when doing benchmarks.
What exactly would cause a penalty here? Simply a non empty watchPaths, or watchPaths pointing to empty directories, or using reload instead of redeploy ?
c
cy
01/08/2020, 10:17 AM
Every request does up-to-date check and this is done under lock so it will reduce concurrency. This feature is only suitable for quick development and debugging.
cy
01/08/2020, 10:23 AM
However, empty watch paths disables this checks so no penalty.
cy
01/08/2020, 10:27 AM
What is your usecase? Why do you think you need it in production?
s
spand
01/08/2020, 10:32 AM
No, but I think we have it non empty on production but pointing to nonexisting directories
c
cy
01/08/2020, 10:40 AM
I believe it will be disabled in this case as well