Mongodb - Connection Pool size not reflecting












0















Mongodb has default connection poll size eq 5 .



I have a problem with connection pool size always equal 1 if I connect to mongodb by mongodb client and equal 2 if I connect to mongodb by mongoose



regarding to mongoose if I set poolSize=1 the connection poolSize will be one, if I tried to make it higher than two the poolSize will be two only



I also set maxPoolSize for mongoose and mongodb client, not reflecting !!



I am checking connection pool size from mongodb server by command
"db.serverStatus().connections"



However If I logged form client (connections.length) it's always equal 1 , for mongoose and mongodb client as well



I want to know if there is configuration for mongodb server or the operating system " Debian 9 " to update max pool size



I have tried many ways to set poolSize ( By add it as query param or options object )



Mongodb performance is too bad ->



I was testing express http server by jmeter by sending request from one thread infinite loop the throughput was 12000 +
the response was static hello world text



after adding mongoose and send response ( find all records in table has only 5 records ) the throughput is 600+ only



So I would like to know how to maximize connection pool and hacks to enhance mongoose performance



Ps: I have changed ulimit open files to be 64000



Mongoose connection code :



mongoose.connect(dbUrl , {  useNewUrlParser: true  , 
autoReconnect:true ,
poolSize: 100,
reconnectInterval: 1000,
reconnectTries: 30
});
var db = mongoose.connection;
db.once('open', function() {
console.log(mongoose.connections.length);
});


Mongodb Client code :



var MongoClient = require('mongodb').MongoClient;
MongoClient.connect(dbUrl, {
useNewUrlParser: true ,
poolSize: 1000
}, function(err, client) {

!err ? console.log('') :console.log(client);
});









share|improve this question



























    0















    Mongodb has default connection poll size eq 5 .



    I have a problem with connection pool size always equal 1 if I connect to mongodb by mongodb client and equal 2 if I connect to mongodb by mongoose



    regarding to mongoose if I set poolSize=1 the connection poolSize will be one, if I tried to make it higher than two the poolSize will be two only



    I also set maxPoolSize for mongoose and mongodb client, not reflecting !!



    I am checking connection pool size from mongodb server by command
    "db.serverStatus().connections"



    However If I logged form client (connections.length) it's always equal 1 , for mongoose and mongodb client as well



    I want to know if there is configuration for mongodb server or the operating system " Debian 9 " to update max pool size



    I have tried many ways to set poolSize ( By add it as query param or options object )



    Mongodb performance is too bad ->



    I was testing express http server by jmeter by sending request from one thread infinite loop the throughput was 12000 +
    the response was static hello world text



    after adding mongoose and send response ( find all records in table has only 5 records ) the throughput is 600+ only



    So I would like to know how to maximize connection pool and hacks to enhance mongoose performance



    Ps: I have changed ulimit open files to be 64000



    Mongoose connection code :



    mongoose.connect(dbUrl , {  useNewUrlParser: true  , 
    autoReconnect:true ,
    poolSize: 100,
    reconnectInterval: 1000,
    reconnectTries: 30
    });
    var db = mongoose.connection;
    db.once('open', function() {
    console.log(mongoose.connections.length);
    });


    Mongodb Client code :



    var MongoClient = require('mongodb').MongoClient;
    MongoClient.connect(dbUrl, {
    useNewUrlParser: true ,
    poolSize: 1000
    }, function(err, client) {

    !err ? console.log('') :console.log(client);
    });









    share|improve this question

























      0












      0








      0








      Mongodb has default connection poll size eq 5 .



      I have a problem with connection pool size always equal 1 if I connect to mongodb by mongodb client and equal 2 if I connect to mongodb by mongoose



      regarding to mongoose if I set poolSize=1 the connection poolSize will be one, if I tried to make it higher than two the poolSize will be two only



      I also set maxPoolSize for mongoose and mongodb client, not reflecting !!



      I am checking connection pool size from mongodb server by command
      "db.serverStatus().connections"



      However If I logged form client (connections.length) it's always equal 1 , for mongoose and mongodb client as well



      I want to know if there is configuration for mongodb server or the operating system " Debian 9 " to update max pool size



      I have tried many ways to set poolSize ( By add it as query param or options object )



      Mongodb performance is too bad ->



      I was testing express http server by jmeter by sending request from one thread infinite loop the throughput was 12000 +
      the response was static hello world text



      after adding mongoose and send response ( find all records in table has only 5 records ) the throughput is 600+ only



      So I would like to know how to maximize connection pool and hacks to enhance mongoose performance



      Ps: I have changed ulimit open files to be 64000



      Mongoose connection code :



      mongoose.connect(dbUrl , {  useNewUrlParser: true  , 
      autoReconnect:true ,
      poolSize: 100,
      reconnectInterval: 1000,
      reconnectTries: 30
      });
      var db = mongoose.connection;
      db.once('open', function() {
      console.log(mongoose.connections.length);
      });


      Mongodb Client code :



      var MongoClient = require('mongodb').MongoClient;
      MongoClient.connect(dbUrl, {
      useNewUrlParser: true ,
      poolSize: 1000
      }, function(err, client) {

      !err ? console.log('') :console.log(client);
      });









      share|improve this question














      Mongodb has default connection poll size eq 5 .



      I have a problem with connection pool size always equal 1 if I connect to mongodb by mongodb client and equal 2 if I connect to mongodb by mongoose



      regarding to mongoose if I set poolSize=1 the connection poolSize will be one, if I tried to make it higher than two the poolSize will be two only



      I also set maxPoolSize for mongoose and mongodb client, not reflecting !!



      I am checking connection pool size from mongodb server by command
      "db.serverStatus().connections"



      However If I logged form client (connections.length) it's always equal 1 , for mongoose and mongodb client as well



      I want to know if there is configuration for mongodb server or the operating system " Debian 9 " to update max pool size



      I have tried many ways to set poolSize ( By add it as query param or options object )



      Mongodb performance is too bad ->



      I was testing express http server by jmeter by sending request from one thread infinite loop the throughput was 12000 +
      the response was static hello world text



      after adding mongoose and send response ( find all records in table has only 5 records ) the throughput is 600+ only



      So I would like to know how to maximize connection pool and hacks to enhance mongoose performance



      Ps: I have changed ulimit open files to be 64000



      Mongoose connection code :



      mongoose.connect(dbUrl , {  useNewUrlParser: true  , 
      autoReconnect:true ,
      poolSize: 100,
      reconnectInterval: 1000,
      reconnectTries: 30
      });
      var db = mongoose.connection;
      db.once('open', function() {
      console.log(mongoose.connections.length);
      });


      Mongodb Client code :



      var MongoClient = require('mongodb').MongoClient;
      MongoClient.connect(dbUrl, {
      useNewUrlParser: true ,
      poolSize: 1000
      }, function(err, client) {

      !err ? console.log('') :console.log(client);
      });






      node.js mongodb mongoose






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 21 '18 at 12:39









      Yasser MasYasser Mas

      112




      112
























          0






          active

          oldest

          votes











          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%2f53412224%2fmongodb-connection-pool-size-not-reflecting%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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%2f53412224%2fmongodb-connection-pool-size-not-reflecting%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

          鏡平學校

          ꓛꓣだゔៀៅຸ໢ທຮ໕໒ ,ໂ'໥໓າ໼ឨឲ៵៭ៈゎゔit''䖳𥁄卿' ☨₤₨こゎもょの;ꜹꟚꞖꞵꟅꞛေၦေɯ,ɨɡ𛃵𛁹ޝ޳ޠ޾,ޤޒޯ޾𫝒𫠁သ𛅤チョ'サノބޘދ𛁐ᶿᶇᶀᶋᶠ㨑㽹⻮ꧬ꧹؍۩وَؠ㇕㇃㇪ ㇦㇋㇋ṜẰᵡᴠ 軌ᵕ搜۳ٰޗޮ޷ސޯ𫖾𫅀ल, ꙭ꙰ꚅꙁꚊꞻꝔ꟠Ꝭㄤﺟޱސꧨꧼ꧴ꧯꧽ꧲ꧯ'⽹⽭⾁⿞⼳⽋២៩ញណើꩯꩤ꩸ꩮᶻᶺᶧᶂ𫳲𫪭𬸄𫵰𬖩𬫣𬊉ၲ𛅬㕦䬺𫝌𫝼,,𫟖𫞽ហៅ஫㆔ాఆఅꙒꚞꙍ,Ꙟ꙱エ ,ポテ,フࢰࢯ𫟠𫞶 𫝤𫟠ﺕﹱﻜﻣ𪵕𪭸𪻆𪾩𫔷ġ,ŧآꞪ꟥,ꞔꝻ♚☹⛵𛀌ꬷꭞȄƁƪƬșƦǙǗdžƝǯǧⱦⱰꓕꓢႋ神 ဴ၀க௭எ௫ឫោ ' េㇷㇴㇼ神ㇸㇲㇽㇴㇼㇻㇸ'ㇸㇿㇸㇹㇰㆣꓚꓤ₡₧ ㄨㄟ㄂ㄖㄎ໗ツڒذ₶।ऩछएोञयूटक़कयँृी,冬'𛅢𛅥ㇱㇵㇶ𥄥𦒽𠣧𠊓𧢖𥞘𩔋цѰㄠſtʯʭɿʆʗʍʩɷɛ,əʏダヵㄐㄘR{gỚṖḺờṠṫảḙḭᴮᵏᴘᵀᵷᵕᴜᴏᵾq﮲ﲿﴽﭙ軌ﰬﶚﶧ﫲Ҝжюїкӈㇴffצּ﬘﭅﬈軌'ffistfflſtffतभफɳɰʊɲʎ𛁱𛁖𛁮𛀉 𛂯𛀞నఋŀŲ 𫟲𫠖𫞺ຆຆ ໹້໕໗ๆทԊꧢꧠ꧰ꓱ⿝⼑ŎḬẃẖỐẅ ,ờỰỈỗﮊDžȩꭏꭎꬻ꭮ꬿꭖꭥꭅ㇭神 ⾈ꓵꓑ⺄㄄ㄪㄙㄅㄇstA۵䞽ॶ𫞑𫝄㇉㇇゜軌𩜛𩳠Jﻺ‚Üမ႕ႌႊၐၸဓၞၞၡ៸wyvtᶎᶪᶹစဎ꣡꣰꣢꣤ٗ؋لㇳㇾㇻㇱ㆐㆔,,㆟Ⱶヤマފ޼ޝަݿݞݠݷݐ',ݘ,ݪݙݵ𬝉𬜁𫝨𫞘くせぉて¼óû×ó£…𛅑הㄙくԗԀ5606神45,神796'𪤻𫞧ꓐ㄁ㄘɥɺꓵꓲ3''7034׉ⱦⱠˆ“𫝋ȍ,ꩲ軌꩷ꩶꩧꩫఞ۔فڱێظペサ神ナᴦᵑ47 9238їﻂ䐊䔉㠸﬎ffiﬣ,לּᴷᴦᵛᵽ,ᴨᵤ ᵸᵥᴗᵈꚏꚉꚟ⻆rtǟƴ𬎎

          Why https connections are so slow when debugging (stepping over) in Java?