I am running a python process separate from my actual Django web server to do background processing. Since I need database access and I like using Django's models, I call django.core.management.setup_environ at the start of my background process.
I am now trying to fork the process using the processing module (http://pypi.python.org/pypi/processing) so I can run code on multiple cores concurrently. Specifically, I use the Pool class to create a bunch of worker processes that I can asynchronously assign work to. Each of my worker processes also need DB access via Django's models. Question: Does it make more sense to call setup_environ before or after forking? In particular, I don't know how Django sets up its database connection. Do forked processes share one connection or does each process have their own connection? Are there pros and cons to each? Also, if it matters, I'm currently running MySQL 5.0.5 as the DB. Thanks! -- Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
