QtConcurrent-simple-usage: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
(5 intermediate revisions by 3 users not shown) | |||
Line 1: | Line 1: | ||
[[Category:HowTo]] | |||
This code focuses on the following problem: | |||
We have a '''QList<Params>''' | |||
We need to run some time consuming function for each '''Params''' set on the list. | |||
The single core solution: | |||
<code> | |||
void Optimizer::execute() | |||
{ | |||
QList<Params> params = generateParamsSet(); | |||
QList<Result> results; | |||
for(int i = 0; i < params.size(); +''i) { | |||
results.append( someReallyTimeConsumingFunction(params) ); | |||
} | |||
//... | |||
</code> | |||
Let's use QtConcurrent to scale easily over the cores: | |||
<code> | |||
void Optimizer::execute() | |||
{ | |||
QList<Params> params = generateParamsSet(); | |||
QList<Result> results = QtConcurrent::blockingMapped( params, &Optimizer::calculateStats ); | |||
//... | |||
} | |||
Result Optimizer::calculateStats( const Params ¶ms ) | |||
{ | |||
return someReallyTimeConsumingFunction( params ); //this function returns the Result object. | |||
} | |||
</code> | |||
Using it that way, we are sure that none of the cores is bored during our processing! | Using it that way, we are sure that none of the cores is bored during our processing! | ||
To make sure that our code always compiles, even when QtConcurrent is not supported, we may write something like this: | To make sure that our code always compiles, even when QtConcurrent is not supported, we may write something like this: | ||
<code> | |||
void Optimizer::execute() | |||
{ | |||
QList<Params> params = generateParamsSet(); | |||
QList<Result> results; | |||
#ifndef QT_NO_CONCURRENT | |||
results = QtConcurrent::blockingMapped( params, &Optimizer::calculateStats ); | |||
#else | |||
for(int i = 0; i < params.size();''+i) { | |||
results.append( someReallyTimeConsumingFunction(params) ); | |||
} | |||
#endif | |||
//... | |||
} | |||
</code> |
Latest revision as of 21:48, 7 April 2016
This code focuses on the following problem: We have a QList<Params> We need to run some time consuming function for each Params set on the list.
The single core solution:
void Optimizer::execute()
{
QList<Params> params = generateParamsSet();
QList<Result> results;
for(int i = 0; i < params.size(); +''i) {
results.append( someReallyTimeConsumingFunction(params) );
}
//...
Let's use QtConcurrent to scale easily over the cores:
void Optimizer::execute()
{
QList<Params> params = generateParamsSet();
QList<Result> results = QtConcurrent::blockingMapped( params, &Optimizer::calculateStats );
//...
}
Result Optimizer::calculateStats( const Params ¶ms )
{
return someReallyTimeConsumingFunction( params ); //this function returns the Result object.
}
Using it that way, we are sure that none of the cores is bored during our processing!
To make sure that our code always compiles, even when QtConcurrent is not supported, we may write something like this:
void Optimizer::execute()
{
QList<Params> params = generateParamsSet();
QList<Result> results;
#ifndef QT_NO_CONCURRENT
results = QtConcurrent::blockingMapped( params, &Optimizer::calculateStats );
#else
for(int i = 0; i < params.size();''+i) {
results.append( someReallyTimeConsumingFunction(params) );
}
#endif
//...
}