On Apr 19, 11:05 am, Mike <mike.t...@gmail.com> wrote: (...) > Now I want to > move the processing off to a different machine so I'm looking into Celery. > What I'm not sure about is what are the requirements of the workers. Do > they need to have the code they are going to run already installed
Yes. But you can use NFS to avoid having to keep the code in sync on different machines. > or is it > somehow pickled and sent to the worker? No. > My current script checks the DB > for a job, runs the job, and then inserts the data into the django DB. I > guess this won't work with Celery because the remote workers won't have > access to the django DB. Why not ? Neither the django and/or celery processes have to run on the same host as the SQL server, that's what the "HOST" setting is for (https://docs.djangoproject.com/en/1.3/ref/settings/#std:setting-HOST) FWIW, if you start to have performance issues, moving the SQL server process to a different machine might be the first thing to do (depending on where the issues are of course). > I guess the celery tasks should accept data and > only return data - all the interaction with the database should happen on > the web server hosting the django app, right? Nope. Just use the right HOST setting. -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
