[COMPASS-6736] Virtual memory performance appears inaccurate Created: 19/Apr/23  Updated: 14/Jun/23

Status: Open
Project: Compass
Component/s: Real Time Server Stats
Affects Version/s: 1.36.2
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Jason Sturges Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

OS: macOS Monterey 12.6.3 (M1)
node.js / npm versions: v16.19.0 / 8.19.3


Attachments: PNG File Screen Shot 2023-04-19 at 12.29.15 AM.png     PNG File image-2023-05-03-16-47-02-006.png     PNG File image-2023-05-03-16-55-51-497.png    
Story Points: 3

 Description   

Problem Statement/Rationale

Under the performance tab, Compass is reporting 402.53 GB of virtual memory being used.  That's almost my entire SSD, and seems in error.

Steps to Reproduce

Install Compass, connect to a database, go to the performance tab.

No activity, just idle.  Seems to consistently hold this value.

Expected Results

Maybe a unit is off, but I would expect this to be a more reasonable threshold.  Resident memory is 30m, I doubt virtual is ~400 GB.

Also kind of strange there's no unit at the bottom - just says: "402.52" unlike Resident which says: "30m".  Unit is displayed only on the y-axis.

Actual Results

Virtual memory consistently reporting at nearly my entire SSD.  

Additional Notes

This memory visualization presses resident memory to 1-pixel at the bottom of the chart, due to the magnitude of min/max on the y-axis.



 Comments   
Comment by Jason Sturges [ 03/May/23 ]

Hmm... maybe I've not paid attention to how macOS is reporting this.

 

 

Seemingly not related to MongoDB, just how macOS is reporting that.

 

Maybe it's different on Windows, but if this is intended the visualization graph provides no value if actual memory is 15,000x less than virtual.  It's always 1-pixel.

 

Maybe disregard this issue unless you want to consider the visualization.

Comment by Jason Sturges [ 03/May/23 ]

jessica.sigafoos@mongodb.com Were you referring to me or jsivasankara@barclaycardus.com ?

I can provide the entire output, or relevant bits:

  mem: {
      bits: 64,
      resident: 27,
      virtual: 402119,
      supported: true
  },

 

Comment by Jessica Sigafoos [ 03/May/23 ]

jsivasankara@barclaycardus.com, can you run the serverStatus command (https://www.mongodb.com/docs/manual/reference/command/serverStatus/) and share the results with us? Thanks!

Comment by PM Bot [ 19/Apr/23 ]

Hello jason@jasonsturges.com, thank you for reaching out to us! The team will review your issue and get back to you soon as soon as possible.

Please review your issue to ensure you've included your environment details and have attached relevant logs (with any sensitive data redacted), so that we're best able to provide you a timely and thorough response. Thanks again!

Generated at Wed Feb 07 22:44:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.