Re: Do Signals block Django process?

Thanks for the info about django-debug-toolbar. I will certainly test it. I assume that I do a quite a lot of slow queries, but during development I run with a very reduced dataset, so my database (sqlite too instead of mysql) only contains a couple of hundred entries whereas in deployment it

Re: Do Signals block Django process?

On 30 Jan 2015 17:13, "Tobias Dacoir" wrote: > > I just added django-badges to my project. Basically it can award Badges if Users fullfill certain requirements. For this, everytime I call user.save() django-badges receives the post_save() signal and starts checking. > > Now my

Re: Do Signals block Django process?

Thanks for always answering my questions :) I did read the documentation on uWSGI and I think I have an understanding now of workers and threads (from Webserver or uWSGI) and how it handles multiple users. For the signals and badge calculation, I did see celery pop up a couple of times and I

Re: Do Signals block Django process?

The number of threads is determined by the number of workers in your process that is serving the application, not Django itself. For example, if you are using uWSGI to serve the application, then you have a parameter "workers" in its initialization file that sets the number of process to spawn

Do Signals block Django process?

I just added django-badges to my project. Basically it can award Badges if Users fullfill certain requirements. For this, everytime I call user.save() django-badges receives the post_save() signal and starts checking. Now my project is similar to an online quiz, where users submit forms to