I have already reported the proposal decoupling size spooler and buffer.
"...If you think to pass big messages, set a bigger buffer size using the -b
option..."
It seems to me to write a message that it should not matter.
Especially the performance / speed is not as significant here.
I'd like to throw in even some control over the order of operations they
perform.
uwsgi.send_to_spooler({}, priority=4)
priority - optional parameter from 0 to 9
sample Spooler file name:
priority_createdtimestamp_otherstuff
4_1308331780_....
In this case, could be easily sorted by name and obtain a sequence of tasks.
From what I observed out of the sequence of tasks is almost accidental now.
At beginning task should be done by priority, next by date of send task.
--
Łukasz Wróblewski
http://www.nri.pl/ - Nowoczesne Rozwiązania Internetowe
http://www.hostowisko.pl/ - Profesjonalny i tani hosting
http://www.katalog-polskich-firm.pl/ - Najlepszy darmowy katalog firm
_______________________________________________
uWSGI mailing list
[email protected]
http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
