Why does my Azure Function to write to MongoDB Atlas have >70s cold start time?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I wonder whether there is a general problem in my function, which leads to such a long cold start. Mongoose has been installed as a dependency which might increase the time. But 70s?!? Come on...



Here is my code. Quite simple really. Just wanna write some stuff to MongoDB. I appreciate any feedback.






module.exports = function(context, req) {
context.log("Function started!");

// Database interaction.
const mongoose = require('mongoose');
const DATABASE = process.env.MongodbAtlas;

// Connect to our Database and handle any bad connections
mongoose.connect(DATABASE);
mongoose.Promise = global.Promise; // Tell Mongoose to use ES6 promises
mongoose.connection.on('error', (err) => {
context.log(`ERROR→ ${err.message}`);
});

// Portfolio Schema.
require('./portfolioModel');
const Portfolio = mongoose.model('Portfolio');

//Create a Portfolio object.
var portfolio = new Portfolio();
portfolio.fiat = "EUR";
portfolio.token[0] = {
crypto_ticker: "BTC",
crypto_name: "Bitcoin",
crypto_qty: 50,
crypto_invested_sum: 9000
};

// Save to db.
portfolio.save();
context.done();

};












share|improve this question































    0















    I wonder whether there is a general problem in my function, which leads to such a long cold start. Mongoose has been installed as a dependency which might increase the time. But 70s?!? Come on...



    Here is my code. Quite simple really. Just wanna write some stuff to MongoDB. I appreciate any feedback.






    module.exports = function(context, req) {
    context.log("Function started!");

    // Database interaction.
    const mongoose = require('mongoose');
    const DATABASE = process.env.MongodbAtlas;

    // Connect to our Database and handle any bad connections
    mongoose.connect(DATABASE);
    mongoose.Promise = global.Promise; // Tell Mongoose to use ES6 promises
    mongoose.connection.on('error', (err) => {
    context.log(`ERROR→ ${err.message}`);
    });

    // Portfolio Schema.
    require('./portfolioModel');
    const Portfolio = mongoose.model('Portfolio');

    //Create a Portfolio object.
    var portfolio = new Portfolio();
    portfolio.fiat = "EUR";
    portfolio.token[0] = {
    crypto_ticker: "BTC",
    crypto_name: "Bitcoin",
    crypto_qty: 50,
    crypto_invested_sum: 9000
    };

    // Save to db.
    portfolio.save();
    context.done();

    };












    share|improve this question



























      0












      0








      0








      I wonder whether there is a general problem in my function, which leads to such a long cold start. Mongoose has been installed as a dependency which might increase the time. But 70s?!? Come on...



      Here is my code. Quite simple really. Just wanna write some stuff to MongoDB. I appreciate any feedback.






      module.exports = function(context, req) {
      context.log("Function started!");

      // Database interaction.
      const mongoose = require('mongoose');
      const DATABASE = process.env.MongodbAtlas;

      // Connect to our Database and handle any bad connections
      mongoose.connect(DATABASE);
      mongoose.Promise = global.Promise; // Tell Mongoose to use ES6 promises
      mongoose.connection.on('error', (err) => {
      context.log(`ERROR→ ${err.message}`);
      });

      // Portfolio Schema.
      require('./portfolioModel');
      const Portfolio = mongoose.model('Portfolio');

      //Create a Portfolio object.
      var portfolio = new Portfolio();
      portfolio.fiat = "EUR";
      portfolio.token[0] = {
      crypto_ticker: "BTC",
      crypto_name: "Bitcoin",
      crypto_qty: 50,
      crypto_invested_sum: 9000
      };

      // Save to db.
      portfolio.save();
      context.done();

      };












      share|improve this question
















      I wonder whether there is a general problem in my function, which leads to such a long cold start. Mongoose has been installed as a dependency which might increase the time. But 70s?!? Come on...



      Here is my code. Quite simple really. Just wanna write some stuff to MongoDB. I appreciate any feedback.






      module.exports = function(context, req) {
      context.log("Function started!");

      // Database interaction.
      const mongoose = require('mongoose');
      const DATABASE = process.env.MongodbAtlas;

      // Connect to our Database and handle any bad connections
      mongoose.connect(DATABASE);
      mongoose.Promise = global.Promise; // Tell Mongoose to use ES6 promises
      mongoose.connection.on('error', (err) => {
      context.log(`ERROR→ ${err.message}`);
      });

      // Portfolio Schema.
      require('./portfolioModel');
      const Portfolio = mongoose.model('Portfolio');

      //Create a Portfolio object.
      var portfolio = new Portfolio();
      portfolio.fiat = "EUR";
      portfolio.token[0] = {
      crypto_ticker: "BTC",
      crypto_name: "Bitcoin",
      crypto_qty: 50,
      crypto_invested_sum: 9000
      };

      // Save to db.
      portfolio.save();
      context.done();

      };








      module.exports = function(context, req) {
      context.log("Function started!");

      // Database interaction.
      const mongoose = require('mongoose');
      const DATABASE = process.env.MongodbAtlas;

      // Connect to our Database and handle any bad connections
      mongoose.connect(DATABASE);
      mongoose.Promise = global.Promise; // Tell Mongoose to use ES6 promises
      mongoose.connection.on('error', (err) => {
      context.log(`ERROR→ ${err.message}`);
      });

      // Portfolio Schema.
      require('./portfolioModel');
      const Portfolio = mongoose.model('Portfolio');

      //Create a Portfolio object.
      var portfolio = new Portfolio();
      portfolio.fiat = "EUR";
      portfolio.token[0] = {
      crypto_ticker: "BTC",
      crypto_name: "Bitcoin",
      crypto_qty: 50,
      crypto_invested_sum: 9000
      };

      // Save to db.
      portfolio.save();
      context.done();

      };





      module.exports = function(context, req) {
      context.log("Function started!");

      // Database interaction.
      const mongoose = require('mongoose');
      const DATABASE = process.env.MongodbAtlas;

      // Connect to our Database and handle any bad connections
      mongoose.connect(DATABASE);
      mongoose.Promise = global.Promise; // Tell Mongoose to use ES6 promises
      mongoose.connection.on('error', (err) => {
      context.log(`ERROR→ ${err.message}`);
      });

      // Portfolio Schema.
      require('./portfolioModel');
      const Portfolio = mongoose.model('Portfolio');

      //Create a Portfolio object.
      var portfolio = new Portfolio();
      portfolio.fiat = "EUR";
      portfolio.token[0] = {
      crypto_ticker: "BTC",
      crypto_name: "Bitcoin",
      crypto_qty: 50,
      crypto_invested_sum: 9000
      };

      // Save to db.
      portfolio.save();
      context.done();

      };






      node.js mongoose azure-functions mongodb-atlas






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 22 '18 at 18:03







      René K

















      asked Nov 21 '18 at 21:45









      René KRené K

      358




      358
























          1 Answer
          1






          active

          oldest

          votes


















          0














          The cold start time was reduced to around 3s once I used the Azure Functions extension for VS Code. The extension is automatically creating a package file and sets WEBSITE_RUN_FROM_PACKAGE=1 (some in-depth infos regarding packaging).



          Now "Functions as a Service" gets a lot more interesting.






          share|improve this answer
























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420900%2fwhy-does-my-azure-function-to-write-to-mongodb-atlas-have-70s-cold-start-time%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            The cold start time was reduced to around 3s once I used the Azure Functions extension for VS Code. The extension is automatically creating a package file and sets WEBSITE_RUN_FROM_PACKAGE=1 (some in-depth infos regarding packaging).



            Now "Functions as a Service" gets a lot more interesting.






            share|improve this answer




























              0














              The cold start time was reduced to around 3s once I used the Azure Functions extension for VS Code. The extension is automatically creating a package file and sets WEBSITE_RUN_FROM_PACKAGE=1 (some in-depth infos regarding packaging).



              Now "Functions as a Service" gets a lot more interesting.






              share|improve this answer


























                0












                0








                0







                The cold start time was reduced to around 3s once I used the Azure Functions extension for VS Code. The extension is automatically creating a package file and sets WEBSITE_RUN_FROM_PACKAGE=1 (some in-depth infos regarding packaging).



                Now "Functions as a Service" gets a lot more interesting.






                share|improve this answer













                The cold start time was reduced to around 3s once I used the Azure Functions extension for VS Code. The extension is automatically creating a package file and sets WEBSITE_RUN_FROM_PACKAGE=1 (some in-depth infos regarding packaging).



                Now "Functions as a Service" gets a lot more interesting.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 22 '18 at 18:29









                René KRené K

                358




                358
































                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420900%2fwhy-does-my-azure-function-to-write-to-mongodb-atlas-have-70s-cold-start-time%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Guess what letter conforming each word

                    Port of Spain

                    Run scheduled task as local user group (not BUILTIN)