Does QDebug affect performance?
-
I wonder, I print every array when come to me. That is about some information about it. When I stop receive debug is continue.
qDebug() << "FRAME ID : " << frameId << " - RECEIVED : " << _received << " - START INDEX : " << startIndex << " - LAST INDEX : " << startIndex + count << " - INDEX DIFF LAST FRAME : " << startIndex - index_check << " - COUNT : " << count << " - SIZE : " << size << " - FIRST :" << list[0] << " - LAST :" << list[count - 1];Every frame id has nearly 200 array, and I can take unlimited frameid (yes is limited in uint32 but it is restarting when it is max, you know) so, does it affect performance lost ?
-
I wonder, I print every array when come to me. That is about some information about it. When I stop receive debug is continue.
qDebug() << "FRAME ID : " << frameId << " - RECEIVED : " << _received << " - START INDEX : " << startIndex << " - LAST INDEX : " << startIndex + count << " - INDEX DIFF LAST FRAME : " << startIndex - index_check << " - COUNT : " << count << " - SIZE : " << size << " - FIRST :" << list[0] << " - LAST :" << list[count - 1];Every frame id has nearly 200 array, and I can take unlimited frameid (yes is limited in uint32 but it is restarting when it is max, you know) so, does it affect performance lost ?
@Joe-von-Habsburg
Yes outputting anything affects performance to some degree. Whether it matters depends how often you call it and how much it has to print. From Creator I have seenqDebug()information continuing to come out e.g. even after program has exited, so I presume Creator does some buffering of some kind which may affect performance (possibly for the better).Whatever "nearly 200 array" might mean, try not to print the content of many/large arrays if speed is of the essence.
-
Thank you for your reply
