0
different paths of control in a program that a computer might run at the same time if it has parallel processing support for multithread execution.
threads and processes are two ways of supporting multitasking on a uniprocessor or multiprocessing on a multiprocessor. threads are lighter weight: take less OS resources to implement but only support limited protection and security. processes take more OS resources but can support full protection and security. Many operating systems support both processes and threads, allowing each process to have many threads.
Wiki User
∙ 12y ago
Add your answer:
Earn +20 pts
What is the difference between processes and threads?
The memory space, where a given application is executed is called - process. A Process is the memory set aside for an application to be executed in. Within this process the thing, which is really executed is the thread. The key difference is that processes are fully isolated from each other; threads share (heap) memory with other threads running in the same application. Threads share the address space of the process that created it; processes have their own address. Threads have direct access to the data segment of its process; processes have their own copy of the data segment of the parent process. Threads can directly communicate with other threads of its process; processes must use inter-process communication to communicate with sibling processes. Threads have almost no overhead; processes have considerable overhead. New threads are easily created; new processes require duplication of the parent process. Threads can exercise considerable control over threads of the same process; processes can only exercise control over child processes. A great answer to the question can also be found here: (link moved to link section)
If process stop its execution will thread also stop or it will continue to run?
Processes do not execute, it is the threads within a process that actually execute. All processes have at least one thread of execution, the main thread. If the main thread falls from scope, the process ends, taking all threads with it. This can lead to undefined behaviour if the threads are not terminated gracefully from within the main thread before it falls from scope.
Two threads are waiting for keyboard input one in each process Does this problem ever occur in single threaded processes?
Single-threaded processes only have one thread of execution -- therefore it would not be possible to have two processes waiting for input at the same time.
Whats the difference between plumbing pipe threads and conduit pipe threads?
Plumbing pipe threads are squared and conduit pipe threads are tapered.
What is the difference between a Parent Process and Foreground Process?
A parent process is a process that has spawned one or more child processes such that it takes "ownership" of those processes. A foreground process typically means a process that has a user-interface as opposed to a background process which typically does not. Most background processes are services while most foreground processes are applications. It's important to note that the term "process" has a specific meaning in a multi-processing environment. A process is a computer program that has one or more threads of execution. A thread is the machine-level representation of a task and a process may instantiate as many tasks as are required (hardware permitting). All tasks share the same memory space as the process itself, however each task has its own stack for local storage, as well as to enable the thread's function call-and-return mechanism in addition to thread-local exception handling. Every process must have at least one thread of execution typically referred to as the main thread because that is the thread that executes the program's global main function (the entry point of the application) and subsequently instantiates any additional threads required by the main thread. The additional threads are usually called worker threads and any thread can instantiate its own worker threads. Unlike parent/child processes, thread's cannot "own" other threads; the threads are owned by the process. However, it is possible for worker threads to be controlled by other threads in the same process, so in that sense the controlling thread can be said to be a parent thread. When the main function returns, the main thread terminates, however any active threads within the process will continue executing, thus keeping the process "alive". In many cases this would be undesirable particularly if those threads attempt to access shared memory that is released by the main thread. So although there is no notion of ownership amongst threads, any controlling thread that must terminate before its workers have completed their tasks should signal its workers to terminate and then wait for them to terminate before terminating itself. Threads of execution within a process execute concurrently. All this means is that the operating system's task scheduler gives each thread a time-slice of the CPU to do some work, before saving the thread's state and moving onto the next thread (which may belong to another process entirely). Task-switching is so rapid that it can appear as though all threads are executing simultaneously, however that is only physically possible when the CPU has 2 or more cores available. Only one thread may execute upon any single core at any given moment. Multiple threads are typically used to maintain responsiveness. In a GUI environment, a time-consuming task would take up the entire time-slice of a process so it won't be able to respond to any messages on the message queue unless the task specifically checks the queue periodically. However, by using a worker thread to carry out the task, the controlling thread can remain responsive to messages. The message queue can also be used by threads to signal other threads, thus a controlling thread can respond to periodic progress reports from its worker threads if required. In this sense it can be said that the worker threads are background tasks, while the controlling thread is the foreground task.
What is the difference between processes and threads?
The memory space, where a given application is executed is called - process. A Process is the memory set aside for an application to be executed in. Within this process the thing, which is really executed is the thread. The key difference is that processes are fully isolated from each other; threads share (heap) memory with other threads running in the same application. Threads share the address space of the process that created it; processes have their own address. Threads have direct access to the data segment of its process; processes have their own copy of the data segment of the parent process. Threads can directly communicate with other threads of its process; processes must use inter-process communication to communicate with sibling processes. Threads have almost no overhead; processes have considerable overhead. New threads are easily created; new processes require duplication of the parent process. Threads can exercise considerable control over threads of the same process; processes can only exercise control over child processes. A great answer to the question can also be found here: (link moved to link section)
Compare and contrast between threads and classes in java language?
A thread is like any other class, except that there is the capacity to run multiple threads - multiple processes - simultaneously.
What is relationship between process and thread?
Process --1------------m-- Threads 1 process to many threads Bring up your Task Manager (if you are using a windows), Performance tap, you can see the number of process and the number of threads, usually the number of threads is a lot higher than the number of processes.
If process stop its execution will thread also stop or it will continue to run?
Processes do not execute, it is the threads within a process that actually execute. All processes have at least one thread of execution, the main thread. If the main thread falls from scope, the process ends, taking all threads with it. This can lead to undefined behaviour if the threads are not terminated gracefully from within the main thread before it falls from scope.
Why thread is called light weight process?
Threads are implemented by a library that utilizes underlying kernel-supported threads of control, called light-weight processes (LWPs). http://java.icmc.usp.br/books/os/html/threads_lightweight_process.html
Briefly summarise the reasons for the decisions made by software developers regarding the use of processes versus threads?
Control and speed of executions.
Why implementation of threads in Operating Systems is more responsive than processes?
i dont know but i think it cause your computer nono work :)
Two threads are waiting for keyboard input one in each process Does this problem ever occur in single threaded processes?
Single-threaded processes only have one thread of execution -- therefore it would not be possible to have two processes waiting for input at the same time.
Are Word and PowerPoint different processes or threads of a single process?
They are different processes. While both are part of the Microsoft Office suite, and their data is stored in the same area of the Windows Registry, they are two different executable programs. If you open the Task Manager, then click the processes tab, you can see that they are running as different processes.
Why thread used in java?
Threads are used in Java to run multiple operations in parallel. You can create and run multiple threads in parallel to utilize the processing power of the computer and reduce waiting time which would be high if processes are executed in sequence
What is your club penguin account password?
Processes are made of threads; threads within a process can be handled by different processors to improve server performance.
What is quasiparallel?
(computer science) Running multiple threads of control in the same address as though they are (almost) separate processes (except for the shared address space).
