-
Notifications
You must be signed in to change notification settings - Fork 31
Roadmap for this package? #84
Comments
Funcpack was made to address cold start issues for projects that have many files and dependencies. Right now, we're investing in Run-From-Zip, to address this problem. We're still not sure if we're going to continue maintaining funcpack (updating and responding to large issues) or if we will no longer maintain it as we move towards Run-From-Zip being the default experience (you can try it now too using the link above). We'd also love to hear arguments to keep funcpack for user experience reasons too :) |
@mhoeger Thanks for your response. If Run-From-Zip solves the problems, will happy to use it. I will try it on my dev/test env soon and post my feedback. |
Sounds great. Please do keep us posted! |
Hi @mhoeger, Any chance README.md can be updated with more detailed explanation of why favoring of I ran a quick test of It seems that while |
Hey @iyerusad, you nailed it :) Both But to address your original ask - good idea, I'll definitely update the README! |
Awesome! Really helps condense rational when people come looking at options to address cold boot. I will be moving our Azure function deployments to run from package for the other benefits. |
Hi Team, I still can't help but feel we still need this project! |
Sorry for commenting on an old issue, but I'm starting to explore Azure functions and trying to better understand some things around best practice and optimisations. I've been pointed to use "Run from package" but I'm not sure I 100% get it just yet. I usually work with AWS Lambda and I have experience with Webpack. I'm not clear if I should/could also use Webpack with "Run with package". I would normally output my Node.js code to a single Thanks in advance - looking to understand this more but it feels like I'm missing something. |
Hi @chearmstrong ! Thanks for the ping - we generally point to "run from package" because tests showed that webpacking code didn't have a significant impact on cold start. That being said, we haven't run those tests in years now and it would be good to retest.
Currently, we're exploring an approach to function declarations that is code-based and not config-based ( We're avoiding maintaining this repo because it hasn't made the cut in terms of our priorities, and if you can help show that we should be looking into this with more urgency that would be greatly appreciated! I've filed this issue here to kinda track that exploration, although I do want to give the caveat that this issue may not see some love for a little while: Azure/azure-functions-nodejs-worker#340 Let me know if that answered your question or if you have other input! |
@mhoeger Thanks for the reply. I think that makes sense for the most part - much appreciated. It certainly would be good to see if webpacking/bundling does make a difference to cold starts or performance in general. For my own curiosity - is there any documentation that shows how "run from package" actually works, vs. not using that (or using only Thanks in advance, and sorry for so many questions - just trying to fully understand how it works. 🛠 |
No problem! Thanks for the good questions - this post should give good details on "run from package": Azure/app-service-announcements#84 ! |
Hi Team,
Is this package still actively maintained by Azure Team? Last commit was few months back.
With increase in Azure Node.js serverless usage, it would be great if we can upgrade this package.
Thanks.
The text was updated successfully, but these errors were encountered: