> > > The reason why we didn't choose jRuby was because it uses too much > > memory to be able to run this on a VPS. Is there any documentation > > available on using jRuby on a low-memory (<256MB) system? I've looked > > for it, but couldn't find it. Maybe there's an alternative workaround > > for the GIL? Our application uses up quite alot of memory, so when > > presented with the jRuby vs. Ruby (EE) question, I thought it was a > > choice between thread safety and memory usage, so I chose the latter. > > I didn't know there was more to think about. > > > > Regardless, I can't seem to reproduce the OPs behviour: > > > Which Ruby implementation are you using? I'm very sure every thread in > > my piece of code is waiting for the other thread to finish, because I > > log the time at which the data is saved. Most of the time there's 10 - > > 40 seconds between them, even though the backgroundrb process should > > save at least one object every second. > > x...@clover:~/projects$ ruby -v > ruby 1.8.7 (2009-06-12 patchlevel 174) [x86_64-linux] > > Threading's not the issue. Try looking into Lionel's suggestion; > perhaps things will work as expected if you switch to delayed_job > instead of BackgroundRB, or posssssibly even just a different HTTP > client like curb. Or perhaps the problem's not related to the HTTP > fetching at all and we don't have the whole story.
If the problem is in BackgroundRB I'm screwed. This whole system depends on BackgroundRB. It's not just a long-running task, most tasks will run daily for years and years to come. I'll check whether this is related to BackgroundRB and report back. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
