Monday, November 18, 2024
Google search engine
HomeLanguagesThread-based parallelism in Python

Thread-based parallelism in Python

A multi-threaded program consists of sub-programs each of which is handled separately by different threads. Multi-threading allows for parallelism in program execution. All the active threads run concurrently, sharing the CPU resources effectively and thereby, making the program execution faster. Multi-threading is generally used when:

  1. There are sub-programs whose output needs to be combined by the main program.
  2. The main program contains sections of code that are relatively independent of each other.

A multi-threaded program handles different tasks at the same time, within the same process, where different threads share the data space with each other as well as the main thread.

Starting a new thread

The threading module in python provides function calls that is used to create new threads. The __init__ function is used for initializing the data associated with the new threads whereas, the run function defines the thread’s behavior as soon as the thread starts it’s execution.

In order to create a new thread, :

  1. Create a sub class of the thread class.
  2. Override the __init__ function of the thread class. This method will initialize the date specific to a thread.
  3. Override the run method to define the behavior of the thread.




# Python program to demonstrate
# initializing a new thread
import threading
  
class thread(threading.Thread):
    def __init__(self, thread_name, thread_ID):
        threading.Thread.__init__(self)
        self.thread_name = thread_name
        self.thread_ID = thread_ID
    def run(self):
        print(str(self.thread_name) +"  "+ str(self.thread_ID));
  
thread1 = thread("GFG", 1000)
thread2 = thread("Lazyroar", 2000);
  
thread1.start()
thread2.start()
  
print("Exit")


Output:

GFG 1000
Lazyroar 2000
Exit

Threading module

Threading module in python provides powerful and high level support for threads.

Threading module defines the following function calls that is used to obtain thread related data. All these functions are executed atomically.

  1. active_count(): Return the number of Thread objects currently alive. The returned count is equal to the length of the list returned by enumerate().
    Syntax:

    threading.active_count()
  2. current_thread(): Return the current Thread object, corresponding to the caller’s thread of control. If the caller’s thread of control was not created through the threading module, a dummy thread object with limited functionality is returned.
    Syntax:

    threading.current_thread()
  3. get_ident(): Return the ‘thread identifier’ of the current thread. This is a nonzero integer. Its value has no direct meaning; it is intended as a magic cookie to be used e.g. to index a dictionary of thread-specific data. Thread identifiers may be recycled when a thread exits and another thread is created.
    Syntax:

    threading.get_ident()
  4. enumerate(): Return a list of all Thread objects currently alive. The list includes daemonic threads, dummy thread objects created by current_thread(), and the main thread. It excludes terminated threads and threads that have not yet been started.
    Syntax:

    threading.enumerate()
  5. main_thread(): Return the main Thread object. In normal conditions, the main thread is the thread from which the Python interpreter was started.
    Syntax:

    threading.main_thread()
  6. settrace(func): Set a trace function for all threads started from the threading module. The func will be passed to sys.settrace() for each thread, before its run() method is called.
    Syntax:

    threading.settrace(func)
  7. setprofile(func): Set a profile function for all threads started from the threading module. The func will be passed to sys.setprofile() for each thread, before its run() method is called.
    Syntax:

    threading.setprofile(func)
  8. stack_size([size]): Return the thread stack size used when creating new threads.
    Syntax:

    threading.stack_size([size])

This module also includes the constant:

  • TIMEOUT_MAX: The maximum value allowed for the timeout parameter of blocking functions (Lock.acquire(), RLock.acquire(), Condition.wait(), etc.). Specifying a timeout greater than this value will raise an OverflowError.
    Syntax:

    threading.TIMEOUT_MAX




# Python program to demonstrate
# threading module
import threading
  
def trace_function():
    print("Passing the trace function")
def profile():
    print("Setting the profile of thread: " + str(threading.current_thread().getName()))
  
class thread(threading.Thread):
    def __init__(self, thread_name, thread_ID):
        threading.Thread.__init__(self)
        self.thread_name = thread_name
        self.thread_ID = thread_ID
    def run(self):
        print(str(self.thread_ID));
        print("Number of active threads: "+ str(threading.active_count()))
        print("Name of current thread: " + str(threading.current_thread().getName()))
                                                 
  
  
thread1 = thread("GFG", 1000)
thread2 = thread("Lazyroar", 2000);
print("Name of main thread: " + str(threading.main_thread().getName()))
print("Identity of main thread: "+ str(threading.get_ident()))
print("Stack size = " + str(threading.stack_size()))
print(threading.settrace(trace_function()))
threading.setprofile(profile())
  
  
thread1.start()
thread2.start()
print("Enumeration list: ")
print(threading.enumerate())
print("Exit")


Output:

Name of main thread: MainThread
Identity of main thread: 139964150720320
Stack size = 0
Passing the trace function
None
Setting the profile of thread: MainThread
1000
Number of active threads: 2
Name of current thread: Thread-1
2000
Number of active threads: 2
Name of current thread: Thread-2
Enumeration list: 
[]
Exit

Reference:

This article is contributed by Mayank Kumar. If you like Lazyroar and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to contribute@geeksforgeeks.org. See your article appearing on the Lazyroar main page and help other Geeks.

Please write comments if you find anything incorrect, or you want to share more information about the topic discussed above.

Dominic Rubhabha-Wardslaus
Dominic Rubhabha-Wardslaushttp://wardslaus.com
infosec,malicious & dos attacks generator, boot rom exploit philanthropist , wild hacker , game developer,
RELATED ARTICLES

Most Popular

Recent Comments