Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Process and thread are not Qt-specific concepts. You can search for "process vs. thread" anywhere for that distinction to be explained. For instance: <a href="https://stackoverflow.com/questions/1762418/process-vs-thread">What resources are shared between threads?</a></p> <p>Though related concepts, spawning a new process is a more "heavyweight" form of parallelism than spawning a new thread within your existing process. Processes are protected from each other by default, while threads of execution <em>within</em> a process can read and write each other's memory directly. The protection you get from spawning processes comes at a greater run-time cost...and since independent processes can't read each other's memory, you have to share data between them using methods of <a href="http://en.wikipedia.org/wiki/Inter-process_communication" rel="nofollow noreferrer">inter-process communication</a>.</p> <p>Odds are that you want threads, because they're simpler to use in a case where one is writing all the code in a program. Given all the complexities in multithreaded programming, I'd suggest looking at a good book or reading some websites to start with. See: <a href="https://stackoverflow.com/questions/2482/what-are-some-good-resources-for-learning-threaded-programming">What are some good resources for learning threaded programming?</a></p> <p>But if you want to dive in and just get a feel for how threading in Qt looks, you can spend time looking at the examples:</p> <p><a href="http://qt-project.org/doc/qt-4.8/examples-threadandconcurrent.html" rel="nofollow noreferrer">http://qt-project.org/doc/qt-4.8/examples-threadandconcurrent.html</a></p> <p>QtConcurrent is an abstraction library that makes it easier to implement some kinds of parallel programming patterns. It's built on top of the QThread abstractions, and there's nothing it can do that you couldn't code yourself by writing to QThread directly. But it might make your code easier to write and less prone to errors.</p> <p>As for an event loop...that is merely a generic term for how any given thread of execution in your program waits for work items to process, processes them, and can decide when it is no longer needed. If a thread's job were merely to start up, do some math, and exit...then it wouldn't need an event loop. But starting and stopping a thread takes time and churns resources. So typically threads live for longer periods of time, and have an event loop that knows how to wait for events it needs to respond to.</p> <p>If you build on top of QtConcurrent, you won't have to worry about an event loop in your worker threads because they are managed automatically in a thread pool. The word count example is pretty simple to see:</p> <p><a href="http://qt-project.org/doc/qt-4.8/qtconcurrent-wordcount-main-cpp.html" rel="nofollow noreferrer">http://qt-project.org/doc/qt-4.8/qtconcurrent-wordcount-main-cpp.html</a></p>
    singulars
    1. This table or related slice is empty.
    1. POQProcess, QEventLoop - of any use for parallel-processing
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USHostileFork
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POQProcess, QEventLoop - of any use for parallel-processing
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for interesting comments and refs.
      singulars
      1. PO
      1. USoctoback
    2. CODo you have an hint why should implementation of multithreading with QtConcurrent have some interaction with presence of QTime objects in the code. It is what seems to happen in my code. With Qtime::start() and Qtime::elapsed() methods called before and after 'multithreaded code', it works ; without, I have no time improvement compared with async. implementation, so that I figure out parallelization does not work then. Thanks.
      singulars
      1. PO
      1. USoctoback
    3. COParallelization isn't always a win for performance, especially in trivial tasks. I saw another question from you about the generation of 2000 random coordinate pairs...and I wouldn't be surprised if the overhead of distributing that work to threads and re-gathering it was *slower* than doing it on a single thread. Make sure your tasks are *actually* running simultaneously by putting in some printed debug output and ensure that it is interwoven; use a slower task so you are sure to see speedup on a multi-core machine.
      singulars
      1. PO
      1. USHostileFork
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload