Comparative Performance of Operating Systems in Handling Sentiment Analysis REST API Workloads
DOI:
https://doi.org/10.15408/jti.v19i2.50125Keywords:
Context Switching, CPU Scheduling, REST API, Sentiment Analysis, Tail LatencyAbstract
This study evaluates the performance of a sentiment analysis REST API deployed across different operating system environments, with particular attention to tail latency and available operating-system-level execution indicators. The study examines how differences in platform-level execution conditions and scheduling-related behavior may be associated with variations in service performance under parallel workloads. Comparative experiments were conducted using Apache JMeter with incremental concurrency, while available system monitoring data were used to observe context switching and CPU utilization patterns. All recorded scenarios achieved a 0% error rate. In the available Windows Server and Ubuntu results, Ubuntu exhibited a lower P99 latency (179.40 ms) than Windows Server (416.53 ms), although Ubuntu experienced a single extreme maximum latency spike of 1792 ms. Ubuntu monitoring data also indicated uneven CPU utilization, with one core reaching 91.69%, suggesting a potential workload concentration issue. Windows Server exhibited a higher P99 latency together with context switching peaks of 2765 per second. The macOS results showed lower recorded latency values; however, because the available test conditions did not achieve equivalent workload parameters and synchronized monitoring across all platforms, these findings are interpreted descriptively rather than as evidence of superior operating-system or scheduler efficiency. Overall, the results demonstrate the value of interpreting application-level latency together with available operating-system-level indicators when evaluating REST API deployment performance. The findings further identify worker configuration, CPU affinity, and background process isolation as potential areas for future optimization and controlled experimental validation.
References
[1] “Docker Performance Evaluation across Operating Systems,” Applied Sciences, vol. 14, no. 15, p. 6672, 2024, doi: 10.3390/app14156672.
[2] M. González-Rodríguez, L. Otero-Cerdeira, E. González-Rufino, and F. J. Rodríguez-Martínez, “Study and evaluation of CPU scheduling algorithms,” Heliyon, vol. 10, no. 9, p. e29959, 2024, doi: 10.1016/j.heliyon.2024.e29959.
[3] B. Cai et al., “AutoMan: Resource-efficient provisioning with tail latency guarantees for microservices,” Future Generation Computer Systems, 2023, doi: 10.1016/j.future.2023.01.014.
[4] H. Rodrigues, A. Rito Silva, and A. Avritzer, “Assessment of performance and its scalability in microservice architectures: Systematic literature review,” Journal of Systems and Software, vol. 230, p. 112500, 2025, doi: 10.1016/j.jss.2025.112500.
[5] A. Lawi, E. Prasetyo, and A. Hajar, “Evaluating GraphQL and REST API Services Performance in a Massive and Intensive Accessible Information System,” Computers, vol. 10, no. 11, p. 138, 2021, doi: 10.3390/computers10110138.
[6] A. Golmohammadi, M. Zhang, and A. Arcuri, “Testing RESTful APIs: A Survey,” ACM Transactions on Software Engineering and Methodology, 2023, doi: 10.1145/3617175.
[7] R. Meyer, E. P. da Silva, L. E. Kirchoff, and C. A. F. De Rose, “IADA: A dynamic interference-aware cloud scheduling architecture for latency-sensitive workloads,” Journal of Systems and Software, vol. 194, p. 111491, 2022, doi: 10.1016/j.jss.2022.111491.
[8] Z. Wang, H. Li, L. Sun, S. Rosenkrantz, H. Che, and H. Jiang, “A Tail Latency SLO Guaranteed Task Scheduling Scheme for User-Facing Services,” IEEE Transactions on Parallel and Distributed Systems, vol. 36, no. 4, pp. 759–774, Apr. 2025, doi: 10.1109/TPDS.2025.3542638.
[9] H. Liao, T.-Y. Liu, J. Guo, B. Huang, D. Yang, and J. Ding, “Retrospecting Available CPU Resources: SMT-Aware Scheduling to Prevent SLA Violations in Data Centers,” IEEE Transactions on Parallel and Distributed Systems, vol. 36, no. 1, pp. 67–83, Jan. 2025, doi: 10.1109/TPDS.2024.3494879.
[10] F. Wiedner, M. Helm, A. Daichendt, J. Andre, and G. Carle, “Performance evaluation of containers for low-latency packet processing in virtualized network environments,” Performance Evaluation, vol. 166C, p. 102442, 2024.
[11] L. Faber, S. L. Vadlamani, and A. v. Kistowski, “Benchmarking Microservices: A Systematic Literature Review of Current Approaches and Metrics,” IEEE Access, vol. 12, pp. 24560–24585, 2024, doi: 10.1109/ACCESS.2024.3364021.
[12] J. Vargas, E. Guerra, and J. de Lara, “Automated Performance Testing of Web Applications: A Systematic Mapping Study,” Automated Software Engineering, vol. 30, no. 1, p. 8, 2023, doi: 10.1007/s10515-022-00373-w.
[13] Y. Hammad, A. A. S. Ahmad, and P. Andras, “An empirical study on the performance overhead of code instrumentation in containerised microservices,” Journal of Systems and Software, vol. 230, p. 112573, 2025, doi: 10.1016/j.jss.2025.112573.
[14] J. Li, Y. Liu, and K. Li, “Tail Latency in Cloud-Scale Services: A Comprehensive Survey of Causes and Solutions,” ACM Computing Surveys, vol. 56, no. 3, pp. 1–36, 2024, doi: 10.1145/3638291.
[15] N. Zhao et al., “Scheduling virtual machines and containers: A comparative review of techniques, performance, and future trends,” Journal of Systems Architecture, vol. 168, p. 103583, 2025, doi: 10.1016/j.sysarc.2025.103583.
[16] M. Niswar et al., “Performance Evaluation of Microservices Communication with REST, GraphQL and gRPC,” Bulletin of the Polish Academy of Sciences: Technical Sciences, vol. 72, no. 2, 2024.
[17] T. Heer, “Comparative Analysis of Load Testing Tools: Apache JMeter vs. K6,” Journal of Web Engineering, vol. 21, no. 6, pp. 1823–1840, 2022, doi: 10.13052/jwe1540-9589.2165.
[18] A. A. A. J. Al-Jumaili, “Performance Evaluation of RESTful Web Services using JMeter,” International Journal of Advanced Computer Science and Applications, vol. 14, no. 8, pp. 605–612, 2023, doi: 10.14569/IJACSA.2023.0140868.
Downloads
Published
Issue
Section
License
Copyright (c) 2026 Jody and Imelda

This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

