Python Overheads Using Ackermann Function Benchmark: Performance and Power Consumption

The main focus of this manuscript is on the impact of running Python codes in two different environments. Firstly, the Python Integrated Development and Learning Environment (IDLE), and secondly, running the same scripts on Windows Command Prompt (CMD). Due to its complexity and demanding nature, on...

Ausführliche Beschreibung

Gespeichert in:
Bibliographische Detailangaben
Veröffentlicht in:Integrated STEM Education Conference (Online) S. 1 - 4
Hauptverfasser: Ghabzouri, Mohammad El, Salhi, Abdenacer Es
Format: Tagungsbericht
Sprache:Englisch
Veröffentlicht: IEEE 15.03.2025
Schlagworte:
ISSN:2473-7623
Online-Zugang:Volltext
Tags: Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
Beschreibung
Zusammenfassung:The main focus of this manuscript is on the impact of running Python codes in two different environments. Firstly, the Python Integrated Development and Learning Environment (IDLE), and secondly, running the same scripts on Windows Command Prompt (CMD). Due to its complexity and demanding nature, one of the best-known benchmark procedures to inspect the resource bounds is the Ackermann function. This study investigates the differences in hardware and software resource consumption between two execution methods. The first method suggests executing the Ackermann function using a 32-bit Python 3.12.7 interpreter, and the second method would be its execution in the 64-bit CMD using the same 32-bit Python interpreter. The current paper investigates the overhead of Python's IDLE in terms of time and memory usage compared to executing the script under test from the command line interpreter, and how all this add further exploited resources (Overheads). Furthermore, the present work witnesses the power consumption of these two methods. Finally, the results show an insignificant time consumption of the CMD method compared to the first method (using IDLE), For instance, the IDLE takes 3 hours and 31 minutes while the CMD method took only 70 seconds to compute Ackermann A(3,6). Moreover, the optimal power and RAM usage is spotted using the CMD execution method.
ISSN:2473-7623
DOI:10.1109/ISEC64801.2025.11147277