This week I focus my attention on troubleshooting the problem of the application. As I explained in the previous post of the week, there is a few problems in the application and I have found some solution to solve this problems.
Decode signal not exposed in Http Client
I refereed to the previous project of Dr Shawn and find out that there is a pair of code that can solve this problem. This problem arises when we are trying to call any witty function after we made a http client request. This is because it will actively block the current threat when waiting for the http client to complete. This problem can be easily solve by the deferRendering() function in the Wapplication class. This function will defer rendering of the current event response until the resumeRendering() function is called. This can solve the problem of double clicking the button in the application.
Testing the file system Limitation
The file system that I am currently using is XFS file system. I cant search any hard Limit of the maximum number of files that can be created in this file system. Although I was able to find From what I have searched on the web, XFS file system is a revolutionary file system that can support millions of files and manage the free space efficiently.
So far, I have tried to create a million random file with size 4KB in one folder, there is not much problem when I try to manipulate the files.
To do some testing on the XFS file system, first I have to list down the criteria that I am looking for in a file system for the application. In the application, the file system must be able to delete files and copy files with no delay for the process of revocation to run smoothly. Besides that I am also expecting the file system is able to list the file in a fairly fast speed for the user to search for their certificate in the application. Last but not least, file system should be able to create files fast to ensure the process of generating certificate run smooth. To conclude, the feature that I am expecting from this file system is to:
Writing Test Script
Now that I am clear that What I want from a file system, I need to write a test script to test for this feature of the system. To write this script, I first have to learn how to write shell script. I learn the basic of a shell script on this website and I learn up the time command to calculate the time needed for the system to perform the task.
Learning Time command
Time command is a very useful too when you want to know the time taken for the process. I learn most of the time command from the general command menu. The default response of time command will present three data. The first time is the elapse real time of the process in seconds follow by CPU-second (user mode) in seconds and CPU-second (kernel mode). I have chosen the real elapse time to be recorded be cause I am concern with the real response time of the system. To change the output of the response, we can simply use the -f FORMAT option that can be found in the command manual. The format that I have chosen is
“\t%e” for real elapse time. After I get the desired output, I need to pump the output of the data to a CSV file to be able to calculate and make conclusion. I first thought of the > way to pump most of the data from the command line to a text file. But I tried to apply this method in the time command but it can pump the data to the file although the CSV file is created. Then I find the command of -o option that will write the data to the file desired. But it will rewrite that file and replace the previous file content. To solve this, simply add the -a option to append the data to the file instead of rewriting the previous content. With thisI am able to read and collect many samples for a better research.
To add all data to the same CSV file, I simply use the past command to merge lines of files.
The data will then be collected and calculated to determine the optimum number of files in a folder.
For my last week, I will be doing documentation of the application.