Automating GUI Response Time Measurements in Mobile and Web Applications

2019 ◽  
Author(s):  
Nivia Cruz Quental ◽  
Clauirton de Albuquerque Siebra ◽  
Jonysberg Peixoto Quintino ◽  
Fabiana Florentin ◽  
Fabio Queda Bueno da Silva ◽  
...  
Keyword(s):  
Response Time ◽  
Web Applications

Performance Comparison of Web Backend And Database: A Case Study Of Node.JS, Golang and MySQL, MongoDB

2019 ◽  
Vol 13 ◽  
Author(s):  
Faried Effendy ◽  
Taufik ◽  
Bramantyo Adhilaksono
Keyword(s):  
Response Time ◽  
Open Source ◽  
Poisson Distribution ◽  
Mobile Application ◽  
Web Applications ◽  
Performance Comparison ◽  
Memory Usage ◽  
Data Traffic ◽  
Cpu Utilization

: Substantial research has been conducted to compare web servers or to compare databases, but very limited research combines the two. Node.js and Golang (Go) are popular platforms for both web and mobile application back-ends, whereas MySQL and Go are among the best open source databases with different characters. Using MySQL and MongoDB as databases, this study aims to compare the performance of Go and Node.js as web applications back-end regarding response time, CPU utilization, and memory usage. To simulate the actual web server workload, the flow of data traffic on the server follows the Poisson distribution. The result shows that the combination of Go and MySQL is superior in CPU utilization and memory usage, while the Node.js and MySQL combination is superior in response time.

Investigating Factors Influencing the Response Time in ASP.NET Web Applications

2005 ◽  
pp. 223-233 ◽  
Author(s):  
Ágnes Bogárdi-Mészöly ◽  
Zoltán Szitás ◽  
Tihamér Levendovszky ◽  
Hassan Charaf
Keyword(s):  
Response Time ◽  
Web Applications ◽  
Factors Influencing

Caching on the Web

2007 ◽  
pp. 124-158
Author(s):  
Mehregan Mahdavi ◽  
Boualem Bentallah
Keyword(s):  
Response Time ◽  
World Wide ◽  
Web Applications ◽  
Fast Response ◽  
Web Caching ◽  
Web Portals ◽  
Dynamic Data ◽  
Dynamic Content ◽  
The World ◽  
The Web

The World Wide Web provides a means for sharing data and applications among users. However, its performance and in particular providing fast response time is still an issue. Caching is a key technique that addresses some of the performance issues in today’s Web-enabled applications. Deploying dynamic data especially in an emerging class of Web applications, called Web Portals, makes caching even more interesting. In this chapter, we study Web caching techniques with focus on dynamic content. We also discuss the limitations of caching in Web portals and study a solution that addresses these limitations. The solution is based on the collaboration between the portal and its providers.

scholarly journals Graph Based Workload Driven Partitioning System by using MongoDB

2018 ◽  
Vol 7 (1) ◽  
pp. 29
Author(s):  
Arvind Sahu ◽  
Swati Ahirrao
Keyword(s):  
Response Time ◽  
Graph Partitioning ◽  
Social Networking Sites ◽  
Web Applications ◽  
Good Choice ◽  
Data Partitioning ◽  
Graph Representation ◽  
Single Server ◽  
Graph Database ◽  
Time Data

<p>The web applications and websites of the enterprises are accessed by a huge number of users with the expectation of reliability and high availability. Social networking sites are generating the data exponentially large amount of data. It is a challenging task to store data efficiently. SQL and NoSQL are mostly used to store data. As RDBMS cannot handle the unstructured data and huge volume of data, so NoSQL is better choice for web applications. Graph database is one of the efficient ways to store data in NoSQL. Graph database allows us to store data in the form of relation. In Graph representation each tuple is represented by node and the relationship is represented by edge. But, to handle the exponentially growth of data into a single server might decrease the performance and increases the response time. Data partitioning is a good choice to maintain a moderate performance even the workload increases. There are many data partitioning techniques like Range, Hash and Round robin but they are not efficient for the small transactions that access a less number of tuples. NoSQL data stores provide scalability and availability by using various partitioning methods. To access the Scalability, Graph partitioning is an efficient way that can be easily represent and process that data. To balance the load data are partitioned horizontally and allocate data across the geographical available data stores. If the partitions are not formed properly result becomes expensive distributed transactions in terms of response time. So the partitioning of the tuple should be based on relation. In proposed system, Schism technique is used for partitioning the Graph. Schism is a workload aware graph partitioning technique. After partitioning the related tuples should come into a single partition. The individual node from the graph is mapped to the unique partition. The overall aim of Graph partitioning is to maintain nodes onto different distributed partition so that related data come onto the same cluster.</p>

scholarly journals Impact of the persistence layer implementation methods on application per-formance

2020 ◽  
Vol 17 ◽  
pp. 326-331
Author(s):  
Kamil Siebyła ◽  
Maria Skublewska-Paszkowska
Keyword(s):  
Response Time ◽  
Web Applications ◽  
Application Programming Interface ◽  
Data Access ◽  
Persistence Layer ◽  
Application Programming ◽  
Different Levels ◽  
Programming Interface ◽  
The Way

There are various methods for creating web applications. Each of these methods has different levels of performance. This factor is measurable at every level of the application. The performance of the frontend layer depends on the response time from individual endpoint of the used API (Application Programming Interface). The way the data access will be programmed at a specific endpoint, therefore, determines the performance of the entire application. There are many programming methods that are often time-consuming to implement. This article presents a comparison of the available methods of handling the persistence layer in relation to the efficiency of their implementation.                                                                                    

scholarly journals PENGEMBANGAN MEKANISME OTENTIKASI DAN OTORISASI MANAJEMEN CONFIG PADA KASUS SHARED WEB HOSTING BERBASIS LINUX CONTAINER

2016 ◽  
Vol 1 (2) ◽  
Author(s):  
Saifuddin Saifuddin ◽  
Royyana Muslim Ijtihadie ◽  
Baskoro Adi Pratomo
Keyword(s):  
Operating System ◽  
Response Time ◽  
Web Applications ◽  
Single Server ◽  
Test Results ◽  
Testing Performance ◽  
The Web

A large part of the service provider's website using an operating system Linux, when one of the websites in the Shared web can be taken over, most likely other websites will also be mastered by reading config connecting to the database, the mechanism used to read a config file with the command in linux by default is available, using the command “ln -s” also known by the term “symlink” who can read the directory where the web, although different config directory.The results show config on web applications that are in the directory in a single server can be read using these methods but can not be decoded to read user, password, and dbname, because it has given authorization can be decoded only from the directory already listed. on testing performance for latency, memory, and CPU system be followed, to get good results the previous system. The test results using the cache, the response time generated when accessed simultaneously by 20 click per user amounted to 941.4 ms for the old system and amounted to 786.6 ms.

scholarly journals Performance comparison of programming interfaces on the example of REST API, GraphQL and gRPC

2021 ◽  
Vol 21 ◽  
pp. 356-361
Author(s):  
Mariusz Śliwa ◽  
Beata Pańczyk
Keyword(s):  
Response Time ◽  
Execution Time ◽  
Web Applications ◽  
Performance Comparison ◽  
Performance Tests ◽  
Time Performance ◽  
Data Volume ◽  
Rest Api ◽  
Programming Interfaces ◽  
Made In

The article presents a comparison of the performance of three ways of implementing programming interfaces used in web applications - REST, GraphQL and gRPC. For the purposes of the research, three applications were developed, which were made in each of the indicated technologies and with the same functionalities. The applications were used for performance tests carried out with the use of the k6 tool. The applications are used to measure the execution time, performance and volume of processed data during display and adding operations. The obtained results allowed for the conclusion that the best interface in terms of performance (measured as the number of transactions per second) and server response time is REST. However, in terms of the smallest data volume, gRPC is the best choice.

scholarly journals REST API performance comparison of web applications based on JavaScript programming frameworks

2021 ◽  
Vol 19 ◽  
pp. 121-125
Author(s):  
Marcin Grudniak ◽  
Mariusz Dzieńkowski
Keyword(s):  
Response Time ◽  
Programming Language ◽  
Web Applications ◽  
Performance Comparison ◽  
Large Datasets ◽  
Client Application ◽  
Programming Framework ◽  
Rest Api ◽  
Server Application ◽  
Made In

The aim of the work was to compare two technologies for creating server applications based on the JavaScript programming language. For the purposes of the research, two test applications were created. The first one was built on the basis of the Express programming framework and the second one on the basis of the Hapi framework. The client part of both applications was prepared using the React library. The client and server parts communicated with each other by means of REST API – the universal HTTP interface. The client application sent requests to the server application which then performed basic operations on the MongoDB basis and returned the result. As part of the work, an experiment consisting of four scenarios was developed. In each scenario, a different type of data was taken into consideration: a string of characters, an array, an object and an array of objects. The research focused on the efficiency aspect – measuring the response time of requests during GET, POST, PUT and DELETE operations. The tests were performed on two computers and the measurements were made in two ways: using a single code embedded in test applications and using the Postman tool. The obtained results, after averaging and analyzing them allowed for the conclusion that the Express framework proved to be more efficient than Hapi due to the shorter response time of requests. Only in the scenario where operations with large datasets were performed was the response time of requests at a similar level.

Sign in / Sign up

Export Citation Format

Share Document