Date: 2016-05-25
Recently found a problem in the development process, using two development boards for can network communication, according to experience, the speed of communication should be very fast, the project will be the interface timeout time set to 100ms, in a certain situation, in a short period of time to send multiple requests, such as continuous click multiple buttons, Each click to send the can data, this time there will be a time-out report, tangled for a long time, ruled out a variety of problems, has not been resolved.
Today, a thought, see the project there are many test log logs, using the Qdebug and Str::cerr two ways to print, looking too much too annoying, and then commented out, and then, the miracle happened, unexpectedly not appear in the report of this time-out.
Originally, the string of this kind of log printing, is very resource-intensive, the overall slow down the system response speed, resulting in this situation, special record here, for this kind of related problems of friends to do a hint.
ARM Development Board +QT Learning Path--on the influence of can network communication by log log