Greg, what do you recommend to do async writes? I'm a newbie to async tasks in Rails, but doesn't something like delayed_job ALSO us the database to keep track of jobs?
Greg Willits wrote: > > That would likely indicate that the DB is pretty dern busy fulfilling > reads (though someone should analyse that to prove it). When doing > this kind of logging it often becomes necessary to have a second > database which is optimized for writes to take the continual updates > so that your read/write-infrequent data set is left alone. Those log > writes should also be fired off as an asyncronous task so that the > rest of the page/request is not slowed down waiting for the write to > occur. > > I agree that yanking the DB in favor of in-memory workload doesn't > seem appropriate yet. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
