Bug #255
Optimize QtUiMessageProcessor::checkForHighlight()
0%
Description
This method is currently causing most of Quassel's CPU consumption. I haven't evaluated yet if that's mostly based on its Settings instantiation for every call (see Bug #254) or if the various QRegExp passes are too expensive as well. In any case, this needs to be optimized; for every arriving message, CPU usage jumps up to over 20% on my machine, whereas it keeps low when disabling checkForHighlight.
Related issues
History
#1 Updated by Sputnick over 16 years ago
Has moved from Client to QtUiMessageProcessor.
#2 Updated by TerrorBite over 16 years ago
I don't know if it's related to highlight, but I do know that the longer the Quassel client runs, the more CPU is consumed with each incoming message. Investigate this?
#3 Updated by EgS about 16 years ago
TerrorBite: no this is unrelated. The execution time of this method depends purely on the message that is just being worked on and has no relation to the state of the client. Anyways: we're aware of cpu consumption issues over time.
Sput: is this bug still an open issue?
#4 Updated by Sputnick about 16 years ago
No.