Techniques Display Data in A Visual Database Programming Language

Many techniques of presenting information in programming languages, mainly for data that amounts to less than 100 record data. Moreover, if the data has reached more than 10,000 data, application performance will slow down. This has several factors, one of which is the process or the way data is presented by the code/algorithm in a programming language. The purpose of this paper is to show the effects of comparisons of code/algorithms in presenting data, expected outcome of this comparison of code/algorithm is to demonstrate increasing code/algorithm can present data faster.


Introduction
Science programming is increasing and evolving. Similarly, visualizing data pro-cessed by the result of the application pro-cess, using drill-down or and what-if analy-sis Putra et al., 2020). Programming is a basic skill in computer science; logical thinking is needed to solve problems. In another paper, data collection was carried out by interview (Mukaromah et al., 2018;. In software requirements, data is an important item because it is used by an analyst for describes and views all relationships of objects and information (Pressman, 2010).
Several software development articles use data or track information contained in databases with a limited amount of data. (Nugroho & Putra, 2016;Priambodo et al., 2017) or using a data dummy. This can im-pact the outcomes of software development implementation, the implication is that if you use less than 1000 records of data, then the application or program does not look at any difference in terms of the data pro-cessing capacity of the application, the data display process, and the overall application performance.
Performance testing is used to detect performance issues that could arise from a lack of serverside resources, insufficient network capacity, insufficient database ca-pacities, and defective or weak operating system capacities, poorly built web or desk-top application features, and other prob-lems with hardware or software that can lead to reduced performance of the client-server. The aim is two namely: (1) to under-stand how the system reacts as loading in-creases (i.e., number of users, number of transactions, or total volume of data) and (2) to collect metrics that will lead to per-formance improvement design changes (Pressman, 2010).
Based on the above, this paper provides creation and input on how to show data over 5000 data track records with the ap-propriate algorithm and will be compared to displaying data below 100, the result ob-tained is the speed at which data above 5000 records/data line is displayed. The first experiment uses data that is less than 100 rows of information in this paper using two experiments, and the volume of data above 5000 is used for the second experiment.

Material and Methods
This section will describe software development using prototype methodology and why use it.

Why use prototype methodology
Both the functions and features needed for the software being created are not specified by the client. In other situations, the developer could be uncertain as to the feasibility and ability of the algorithm that applied the adaptability of the operating system, or the shape of the humanmachine interaction. A prototyping paradigm could give the best approach in these, and many other situations. Although prototyping can be implemented as a stand-alone process model, it is more commonly used in the sense of some of the process models described in this chapter as a technique that can be implemented. The prototyping model allows you and other stakeholders to better understand what is to be constructed when specifications are fuzzy, regardless of the way it is implemented (Pressman, 2010). Figure 1 shows the iteration of the methodology of the prototype and a de-scription of each step is given below (Bourque & Fairley, 2014):

Communication
In this stage, identifying the require-ments requested, and describing the areas that must be implemented, in this paper the communication stage is displaying data with large amounts of data with fast re-sults.

Quick plan
Quick plan means that the developer must make plans according to user needs and make display designs and iterations quickly.

Modeling and quick design
The focus of the quick design is on por-traying the facets of the program that will be used by the end-user. Quick design leads to a prototype being built.

Construction of prototyping
In this stage, start implementing the re-sults of the design into an application. In this paper, the construction stages are di-vided into 2, namely: 1. conducting exper-iments with 20 times iteration with the number of data below 20 lines, 2. using da-ta more than 5000 lines.

Construction of prototyping
In this stage, start implementing the re-sults of the design into an application. In this paper, the construction stages are di-vided into 2, namely: 1. conducting exper-iments with 20 times iteration with the number of data below 20 lines, 2. using da-ta more than 5000 lines.

Deployment, delivery, and feedback
The expected results from experiments 1 and 2 are that the algorithm applied can display data faster than other algorithms.

Results and Discussion
This section will describe the result with experiment 1 and experiment 2:

Experiment 1
In the First experiment using 17 rows of data and performed 50 iterations, in Figure 2 we can see time execution Object-2 better than Object-1, with several data Object-1 between Object-2 is the same record. Source code comparison between Object-1 (Figure-3) and Object-2 (Figure-4). In Figure-3, the source code is indeed less when compared to Figure-4, but the execution time takes much longer. This is because the source code in Figure 3 uses the syntax ObjectGrid1.DataSource = ds. Tables ("table"). DefaultView means that all data is immediately displayed and executed, while in Figure-4 the source code is indeed more but the result of execution time is faster.
Object 2 has an average execution time of 111ms and it's slightly lower than Object 1 (114ms) (See Figure-5). Object-1. Object-1 tends to increase its execution time when compared to Object-2. Object-1 has a maximum execution time value of 121ms with a minimum value of 110ms, while Object-2 has a maximum execution time value of 119ms and a minimum value of 106ms, for more details can be seen in the Figure-

Conclusion
The results of the study can be concluded that: 1. Based on experiments 1 and 2, this paper succeeds in displaying data quickly using the source code in Object-2. 2. The source code in Object-2 can be applied and used for amounts of data less than 1000 lines or more. 3. Displaying data more than 5000 rows with a query level of more than 1 and a subquery of more than 2, so it's better to use the algorithm on object-2