Monitoring Node-DC-EIS

[octaviansoldea]

trafficstars

During about a month of following Node-DC-EIS benchmark behavior, I observed that many of the performance indicators do not change, many of them are zero, and in some cases they have suspect identical values for various Node.js versions. In this context, I am attaching here my observations in the following xlsx file, in a hope it is self explanatory. NodeJSBenchMarking.xlsx

[mhdawson]

@uttampawar can you take a look or have one of your team take a look?

[octaviansoldea]

Hi @mhdawson and @uttampawar

Following several short discussions on this issue, I would like to update you that I am trying to analyse this in the available time. Meantime I am learning the structure of the code. I anticipate I will be a bit slow on this, however, I will do my best to analyze this issue.

Best regards, @octaviansoldea

[octaviansoldea]

Hi @mhdawson and @uttampawar

This is just a small update. Following a discussion with @uttampawar today we have observed that the node.js version 12 has an issue connecting to mongodb, see also the next excerpt form the log: ... Starting a single instance of Node.js process with (pid: 13241)

---

Server running at port: 9000

---

connect ECONNREFUSED 127.0.0.1:27017 Mongoose connection error. Server exiting ...

Most probably this is due to mongodb version. I will try to reproduce this issue on my computer.

Best regards, @octaviansoldea