<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[How to measure performance improvement of a multi-threaded GUI application?]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I managed to multi-thread a single threaded application. I did this my moving all the classes that performed heavy computations to a separate thread. Then I used the <code>QThread::currentThread()</code>  to ensure functions are executing on the correct thread.</p>
<p dir="auto">The reason behind multi-threading was scalability. In the future this application was planned on having added more computations which could burden the main GUI thread.</p>
<p dir="auto">Now that I've multi-threaded the application how can I measure the improvement in performance?</p>
]]></description><link>https://forum.qt.io/topic/145699/how-to-measure-performance-improvement-of-a-multi-threaded-gui-application</link><generator>RSS for Node</generator><lastBuildDate>Thu, 05 Nov 2026 02:41:11 GMT</lastBuildDate><atom:link href="https://forum.qt.io/topic/145699.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 11 Jun 2023 14:47:28 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to How to measure performance improvement of a multi-threaded GUI application? on Sun, 11 Jun 2023 15:19:24 GMT]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">Which performance are you looking for ?</p>
<p dir="auto">One important note: just throwing threads at your problem is not the solution. You also have to take into account what they do. For example, if you have a disk intensive task and try to run many of them in parallel, you'll quickly see a performance hit because of the speed of the disk.</p>
]]></description><link>https://forum.qt.io/post/761134</link><guid isPermaLink="true">https://forum.qt.io/post/761134</guid><dc:creator><![CDATA[SGaist]]></dc:creator><pubDate>Sun, 11 Jun 2023 15:19:24 GMT</pubDate></item></channel></rss>