fixed typos etc

This commit is contained in:
Ilan Steemers
2015-06-24 12:49:38 +02:00
parent e80e33daa0
commit a6e91b0bcf
2 changed files with 16 additions and 14 deletions
+9 -8
View File
@@ -49,8 +49,8 @@ Admin integration
~~~~~~~~~~~~~~~~~
Django Q registers itself with the admin page to show failed and
succesful tasks. From there task results can be read or deleted. If
neccesary, failed tasks can be reintroduced to the queue.
successful tasks. From there task results can be read or deleted. If
necessary, failed tasks can be reintroduced to the queue.
Signed Tasks
~~~~~~~~~~~~
@@ -66,7 +66,7 @@ Optionally, packages can be compressed before transport by setting
Pusher
~~~~~~
The pusher process continously checks the Redis list for new task
The pusher process continuously checks the Redis list for new task
packages and pushes them on the Task Queue.
Worker
@@ -78,19 +78,20 @@ any of these steps, the package is then pushed onto the Result Queue.
By default Django Q spawns a worker for each detected CPU on the host
system. This can be overridden by setting ``Q_WORKERS = n``. With *n*
being the numbe of desired worker processes.
being the number of desired worker processes.
Monitor
~~~~~~~
The result monitor checks the Result Queue for processed packages and
saves both failed and succesful packages to the Django database.
saves both failed and successful packages to the Django database.
By default only the last 100 succesful packages are kept in the
By default only the last 100 successful packages are kept in the
database. This can be increased or decreased at will by settings
``Q_SAVE_LIMIT = n``. With *n* being the desired number of records. Set
``Q_SAVE_LIMIT = 0`` to save all results to the database. Failed
packages are always saved.
``Q_SAVE_LIMIT = 0`` to save all results to the database.
``Q_SAVE_LIMIT = None`` will make the monitor refrain from savig success
Failed packages are always saved.
Sentinel
~~~~~~~~