Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Readme suggestion: also show memory usage advantage #328

Open
bmahler opened this issue Aug 15, 2023 · 2 comments
Open

Readme suggestion: also show memory usage advantage #328

bmahler opened this issue Aug 15, 2023 · 2 comments

Comments

@bmahler
Copy link

bmahler commented Aug 15, 2023

Currently the readme shows the startup time advantage of this golang client.

The jvm based hdfs client also uses a lot of memory, I would assume this go client has a significant advantage there as well, so would be great to show the difference in memory consumption.

@colinmarc
Copy link
Owner

Hi @bmahler, thanks for the suggestion! Do you have an idea how to measure that in a way that’s pithy to present?

@bmahler
Copy link
Author

bmahler commented Aug 16, 2023

Looks like /usr/bin/time -l on macOS or /usr/bin/time -v on Linux will show the max resident set size

$ /usr/bin/time -lh echo hi                                                                                               [16:03:10]
hi
	0.03s real		0.00s user		0.00s sys
             1081344  maximum resident set size
                   0  average shared memory size
                   0  average unshared data size
                   0  average unshared stack size
                 175  page reclaims
                   1  page faults
                   0  swaps
                   0  block input operations
                   0  block output operations
                   0  messages sent
                   0  messages received
                   0  signals received
                   0  voluntary context switches
                  58  involuntary context switches
             9768055  instructions retired
            16652271  cycles elapsed
              934592  peak memory footprint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants