-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Huge memory usage after upgrading to 2.4.0 #260
Comments
Here's the full diff between 2.3.0 and 2.4.0: jnunemaker/twitter@v2.3.0...v2.4.0 I don't see anything in there that could be leaking memory but let me know if you see things differently. You mentioned that you're not using the gem heavily. Specifically, what methods are you calling and how are you calling them? |
I see nothing suspicious in the diff I'm a bit clueless, but unable to try it again for the time being |
Can you let me know if the problem still existing in version 2.5.0? If that doesn't fix it, could you try 3.0.0.rc.1? I've made a number of performance enhancements. |
Thank u @sferik, I am unable to try this at the time being.. tried 2.4.0 agian using webrick in a side process and things were smooth... trying it (and the newer versions) on our production is expected to be done soon. i'll keep you posted Thank you for your help |
Greetings guys,
I'm not really sure if this is related to the twitter gem. but it is highly probable
After upgrading to the latest 2.4.0 this morning, my passenger workers started using huge memory (4GB+, while normally it used to use 150MB)... after a while of trials and reverting to old code. i noticed that things went back normal after downgrading to 2.3.0 (although i'm not using the gem heavily at all).
I cannot grab the exact problem yet. but I thought of reporting it here, just in case someone faced the same problem:
I'm using rails 3.0.3 on ruby 1.9.2
Here is my complete bundle list
The text was updated successfully, but these errors were encountered: