Response Time for XAMPP Server Based on Different Versions of Linux Operating System

Certes is like the httperf technique but measures the perceived client response time. Software aging is cited as one of the causes of slow response times. Scheduling appropriate system rejuvenation eliminates software aging issues. Task prioritization using the PACERS algorithm eliminates long response times for the essential task. An apache version 1. In so doing it is possible to consider the combination of some of their products to provide fully functioning web systems. One possible combination is the use of the XAMPP server on a Linux operating system. XAMPP is an acronym for Cross-Platform, Apache, MariaDB, PHP, and Perl which is a web development technologies application that was developed by Apache Friends (Kumari & Nandal, 2017). This server can be configured to use mod_ deflate by uncommenting the appropriate directive in the configuration files.

XAMPP is preferred by many developers as its Apache distribution system is light and small. Mosberger and Jin had a preference for httperf over SPECweb and Webstone, since it specializes in server performance and analysis of additional feature performance. Httperf has the capability of sustaining server overloads and collect the requisite statistics. Mosberger and Jin looked at the best ways to design and implement httperf as a performance measuring tool in web servers. Good performance, predictability and ease extensibility were critical factors in implementing httperf in the experiment. Httperf has to be implemented in C for the good performance in critical execution paths. It is clear that server response time can easily be measured efficiently and cheaply using the httperf. On the client side, the performance measurement used is the ClieEnt Response Time Estimated by the Server (Certes).

Certes measure the client perceived response time for web servers. Client perceived response time is integral to a business that desires to understand the effectiveness of their systems to their customers. Olshefski, Nieh, and Agrawal (2002) tried to infer the client response times at the servers. It is of an essence to establish the service level objectives to establish targeted performance in the servers. The response time of a web server is enhanced when the software of a system is at its optimal performance. The aging software is likely to interfere with the response time for XAMPP server. Grotkke et al (2005) explored the aspect of aging software in a web server. The study attempted to build on earlier research that had identified the possibility of ‘software aging’.

Implementing the XAMPP in a Linux system is likely to experience instances of system aging. To ensure that the system functions, a method that can accurately schedule system rejuvenation are required. Grottke et al. (2006), attempted to establish an appropriate time to schedule a system rejuvenation through the use of an artificial workload in predicting system aging. The study explored data on resource usage and activity parameters. To have an efficient XAMPP web server in a Linux operating system, it is essential that the response times are predictable. Predictable response times enable the implementation of accurate provisioning for the XAMPP. Chen, Mohapatra, and Chen (2001) tried to solve the predictability problem using an admission control scheme. The existence of several types of servers and the difference in resource requirements create a prediction problem.

The response times have to be predictable to allow for appropriate web-service provisioning. PACERS algorithm ensures that the server response time is allocated based on task priority. Essential tasks will have quicker and guaranteed response times. Faraj et al (2015) sought to analyze Apache Web Server versions that use the 32 and 64-bit architecture. They tried to establish the optimal server based on the 32 bit or 64-bit architecture. Faraj et al consider the difference between the traditional response time that was based on physical businesses and the automated response time that is based on the web business. The final pairing involved an Easyphp 12. 1 with an Apache 2. The paper aimed to establish the architecture that provided the best apache web server. The results showed that the time response was better for the Apache architecture that could support the Windows operating system.

That was true for both the 32 bit and the 64-bit architecture. Liu et al employed Newton’s method based optimizer and the fuzzy control based optimizer both of which used the hill climbing techniques in optimizing response time. A third technique that did not apply the hill climbing methodology was also used. Instead of the hill climbing approach, the third technique was heuristic and exploited the interactions between time minimization and bottleneck utilization. Online optimization reduced response times better than static schemes to factors that were greater than 10. Research outcomes demonstrated that Newton’s model was incapable of producing consistent results for variable data despite its prominent usage. Previous researchers have concentrated on elements and factors that are connected to response times.

Some of them have gone further to explore response time in Apache Server. No researcher has explored response times on XAMPP in various versions of Linux Operating System. In establishing response time characteristics in various Linux versions, the research aims to improve response times in open source codes. Conclusion Studies on response times have focused on studying the concept of how it relates to servers and not on how it relates to the operating system that supports the servers. Faraj, K. H. A. A. , Ahmad, T. , Vaidyanathan, K. , & Trivedi, K. S. Analysis of software aging in a web server.  IEEE Transactions on reliability, 55(3), 411-420. Liu, X. , Sha, L. , Diao, Y. , Froehlich, S. , Hellerstein, J. Olshefski, D. P. , Nieh, J. , & Agrawal, D.