You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 18, 2019. It is now read-only.
It would be nice to also see a memory consumption comparison. For example the Parallel Ruby implementation got close in speed to the Go sub-string implementation, but Go's goroutines are supposed to have a much lower memory consumption than spawning multiple copies of the Ruby program, so it would be good to see this shown here.
The text was updated successfully, but these errors were encountered:
That is a great point. Go is exceptional at memory management. I'll be sure to address that in my next blog post. If you know of any good CLI tools to measure the memory of a process, and it's subprocesses, let me know. I scoured here (http://unix.stackexchange.com/questions/18841/measuring-ram-usage-of-a-program).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi @dimroc, nice repo and blog posts!
It would be nice to also see a memory consumption comparison. For example the Parallel Ruby implementation got close in speed to the Go sub-string implementation, but Go's goroutines are supposed to have a much lower memory consumption than spawning multiple copies of the Ruby program, so it would be good to see this shown here.
The text was updated successfully, but these errors were encountered: