The PySide.QtCore.QThreadPool class manages a collection of QThreads.
PySide.QtCore.QThreadPool manages and recyles individual PySide.QtCore.QThread objects to help reduce thread creation costs in programs that use threads. Each Qt application has one global PySide.QtCore.QThreadPool object, which can be accessed by calling PySide.QtCore.QThreadPool.globalInstance() .
To use one of the PySide.QtCore.QThreadPool threads, subclass PySide.QtCore.QRunnable and implement the run() virtual function. Then create an object of that class and pass it to QThreadPool.start() .
class HelloWorldTask(QRunnable): def run(self): print "Hello world from thread", QThread.currentThread() hello = HelloWorldTask() # QThreadPool takes ownership and deletes 'hello' automatically QThreadPool.globalInstance().start(hello)PySide.QtCore.QThreadPool deletes the PySide.QtCore.QRunnable automatically by default. Use QRunnable.setAutoDelete() to change the auto-deletion flag.
PySide.QtCore.QThreadPool supports executing the same PySide.QtCore.QRunnable more than once by calling tryStart(this) from within QRunnable.run() . If autoDelete is enabled the PySide.QtCore.QRunnable will be deleted when the last thread exits the run function. Calling PySide.QtCore.QThreadPool.start() multiple times with the same PySide.QtCore.QRunnable when autoDelete is enabled creates a race condition and is not recommended.
Threads that are unused for a certain amount of time will expire. The default expiry timeout is 30000 milliseconds (30 seconds). This can be changed using PySide.QtCore.QThreadPool.setExpiryTimeout() . Setting a negative expiry timeout disables the expiry mechanism.
Call PySide.QtCore.QThreadPool.maxThreadCount() to query the maximum number of threads to be used. If needed, you can change the limit with PySide.QtCore.QThreadPool.setMaxThreadCount() . The default PySide.QtCore.QThreadPool.maxThreadCount() is QThread.idealThreadCount() . The PySide.QtCore.QThreadPool.activeThreadCount() function returns the number of threads currently doing work.
The PySide.QtCore.QThreadPool.reserveThread() function reserves a thread for external use. Use PySide.QtCore.QThreadPool.releaseThread() when your are done with the thread, so that it may be reused. Essentially, these functions temporarily increase or reduce the active thread count and are useful when implementing time-consuming operations that are not visible to the PySide.QtCore.QThreadPool .
Note that PySide.QtCore.QThreadPool is a low-level class for managing threads, see QtConcurrent.run() or the other Qt Concurrent APIs for higher level alternatives.
See also
Parameters: | parent – PySide.QtCore.QObject |
---|
Constructs a thread pool with the given parent .
Return type: | PySide.QtCore.int |
---|
This property represents the number of active threads in the thread pool.
Note
It is possible for this function to return a value that is greater than PySide.QtCore.QThreadPool.maxThreadCount() . See PySide.QtCore.QThreadPool.reserveThread() for more details.
Return type: | PySide.QtCore.int |
---|
Threads that are unused for expiryTimeout milliseconds are considered to have expired and will exit. Such threads will be restarted as needed. The default expiryTimeout is 30000 milliseconds (30 seconds). If expiryTimeout is negative, newly created threads will not expire, e.g., they will not exit until the thread pool is destroyed.
Note that setting expiryTimeout has no effect on already running threads. Only newly created threads will use the new expiryTimeout . We recommend setting the expiryTimeout immediately after creating the thread pool, but before calling PySide.QtCore.QThreadPool.start() .
Return type: | PySide.QtCore.QThreadPool |
---|
Returns the global PySide.QtCore.QThreadPool instance.
Return type: | PySide.QtCore.int |
---|
This property represents the maximum number of threads used by the thread pool.
Note
The thread pool will always use at least 1 thread, even if maxThreadCount limit is zero or negative.
The default maxThreadCount is QThread.idealThreadCount() .
Releases a thread previously reserved by a call to PySide.QtCore.QThreadPool.reserveThread() .
Note
Calling this function without previously reserving a thread temporarily increases PySide.QtCore.QThreadPool.maxThreadCount() . This is useful when a thread goes to sleep waiting for more work, allowing other threads to continue. Be sure to call PySide.QtCore.QThreadPool.reserveThread() when done waiting, so that the thread pool can correctly maintain the PySide.QtCore.QThreadPool.activeThreadCount() .
Reserves one thread, disregarding PySide.QtCore.QThreadPool.activeThreadCount() and PySide.QtCore.QThreadPool.maxThreadCount() .
Once you are done with the thread, call PySide.QtCore.QThreadPool.releaseThread() to allow it to be reused.
Note
This function will always increase the number of active threads. This means that by using this function, it is possible for PySide.QtCore.QThreadPool.activeThreadCount() to return a value greater than PySide.QtCore.QThreadPool.maxThreadCount() .
Parameters: | expiryTimeout – PySide.QtCore.int |
---|
Threads that are unused for expiryTimeout milliseconds are considered to have expired and will exit. Such threads will be restarted as needed. The default expiryTimeout is 30000 milliseconds (30 seconds). If expiryTimeout is negative, newly created threads will not expire, e.g., they will not exit until the thread pool is destroyed.
Note that setting expiryTimeout has no effect on already running threads. Only newly created threads will use the new expiryTimeout . We recommend setting the expiryTimeout immediately after creating the thread pool, but before calling PySide.QtCore.QThreadPool.start() .
Parameters: | maxThreadCount – PySide.QtCore.int |
---|
This property represents the maximum number of threads used by the thread pool.
Note
The thread pool will always use at least 1 thread, even if maxThreadCount limit is zero or negative.
The default maxThreadCount is QThread.idealThreadCount() .
Parameters: |
|
---|
Reserves a thread and uses it to run runnable , unless this thread will make the current thread count exceed PySide.QtCore.QThreadPool.maxThreadCount() . In that case, runnable is added to a run queue instead. The priority argument can be used to control the run queue’s order of execution.
Note that the thread pool takes ownership of the runnable if runnable->autoDelete() returns true, and the runnable will be deleted automatically by the thread pool after the runnable->run() returns. If runnable->autoDelete() returns false, ownership of runnable remains with the caller. Note that changing the auto-deletion on runnable after calling this functions results in undefined behavior.
Parameters: | runnable – PySide.QtCore.QRunnable |
---|---|
Return type: | PySide.QtCore.bool |
Attempts to reserve a thread to run runnable .
If no threads are available at the time of calling, then this function does nothing and returns false. Otherwise, runnable is run immediately using one available thread and this function returns true.
Note that the thread pool takes ownership of the runnable if runnable->autoDelete() returns true, and the runnable will be deleted automatically by the thread pool after the runnable->run() returns. If runnable->autoDelete() returns false, ownership of runnable remains with the caller. Note that changing the auto-deletion on runnable after calling this function results in undefined behavior.
Waits for each thread to exit and removes all threads from the thread pool.
Parameters: | msecs – PySide.QtCore.int |
---|---|
Return type: | PySide.QtCore.bool |
This function overloads PySide.QtCore.QThreadPool.waitForDone() .
Waits up to msecs milliseconds for all threads to exit and removes all threads from the thread pool. Returns true if all threads were removed; otherwise it returns false.