There is another large potential gotcha, R is very memory heavy.
I do think the route of using Celery or other job management tools makes
sense, especially if you can use R across multiple backend machines.
Would celery mean one rpy2 per celery? You don't really want all your
users using the same R session anyways.
Thanks,
Alex
On 04/23/2013 11:08 PM, Derek wrote:
> Thanks Per-Olof
>
> No, it has more to do with the issue raised here:
>
https://github.com/Sleepingwell/DjangoRpyDemo/blob/master/README.md#django-configuration
>
> Possibly Celery could solve that (?) but I really would like to hear from
> someone who actually has a production configuration set up and working.
> Perhaps there are less people in the sciences using Django than I thought...
>
> Derek
>