Monday, April 27, 2015
Hello everyone,
I have a huge problem with memory in Ruby 2.2.1. Namely, after forking a process, it seems that the copy-on-write functionality is not working at all and I end up with double the memory I started with. The problem is described in details under this link : https://bugs.ruby-lang.org/issues/10559#change-50245. Attached on the website is a program that demonstrates the issue.
Since I need to work with huge pieces of data, this memory leakage is a killer issue :-/
Everything has been tested with latest version of Ruby on a clean installed Ubuntu 14.04 LTS machine.
-- I have a huge problem with memory in Ruby 2.2.1. Namely, after forking a process, it seems that the copy-on-write functionality is not working at all and I end up with double the memory I started with. The problem is described in details under this link : https://bugs.ruby-lang.org/issues/10559#change-50245. Attached on the website is a program that demonstrates the issue.
Since I need to work with huge pieces of data, this memory leakage is a killer issue :-/
Everything has been tested with latest version of Ruby on a clean installed Ubuntu 14.04 LTS machine.
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/87b01970-fc8f-4a3a-8fd0-1db3b443508d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment