I can only offer commiseration because I'm in the same position as you ;)
Please let me know what they say.
What do your jobs do?
On Thu, Sep 30, 2010 at 8:58 AM, WilliamF wflana...@tempusgroup.com wrote:
Hi all,
I'm looking for suggestions, as I'm not getting a response from
Heroku.
My
There are some troubleshooting suggestions on this page:
http://docs.heroku.com/ps
On Mon, Oct 4, 2010 at 1:04 PM, Brandon Casci bran...@loudcaster.com wrote:
I can only offer commiseration because I'm in the same position as you ;)
Please let me know what they say.
What do your jobs do?
William...this may sound trivial, but to your DJ workers crash if the work
queues is empty?
On Mon, Oct 4, 2010 at 1:08 PM, Dan Croak dcr...@thoughtbot.com wrote:
There are some troubleshooting suggestions on this page:
http://docs.heroku.com/ps
On Mon, Oct 4, 2010 at 1:04 PM, Brandon
Nope, we love empty queues.
I think it comes down to memory, that we aren't cursoring the output from the
database. We are rewriting our code to implement our own cursor support, since
AR doesn't support it.
The hard part is that we get no information from the process when it crashes.
We
ActiveRecord batches won't work for you?
http://rdoc.info/docs/rails/2.3.8/ActiveRecord/Batches/ClassMethods
Both methods default to 1000 results per batch, but can be configured
with the :batch_size option.
Mike
On Mon, Oct 4, 2010 at 10:56 AM, William Flanagan
wflana...@tempusgroup.com
On Sep 30, 2010, at 3:58 PM, WilliamF wrote:
RPM Monitoring DJ worker host:railgun64.29642 pid:29790
*** Starting job worker host:railgun64.29642 pid:29790
/usr/ruby1.8.7/lib/ruby/1.8/uri/common.rb:385: [BUG] Segmentation
fault
ruby 1.8.7 (2010-04-19 patchlevel 253) [x86_64-linux], MBARI
