> 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.
>
>I have already a request from a customer about this, but the proposal is much more easy to implement: /spooldir /spooldir/1 /spooldir/1/XXXXXXXXXXXXXX /spooldir/2/YYYYYYYYYYYYYY pratically each priority will create a directory that will be processed in order. Tasks in the '1' directory will be processed before task in '2' and so on. (theoretically readdir() should returns file in the order they get created, but it seems to me that is not the case for you) It will be the first thing to implement after 0.9.8.1 release (i suppose on sunday) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
