... h1. Performance Testing and Observability Tools
{toc}
----
h2. Basic Information
* *Project name:* Performance Testing and Observability Tools
* *Short description:* Solaris G11n Performance evaluation, cross operating system comparison, utf8 vs. legacy locales performance, introduction of observability tools available in Solaris/OpenSolaris
* *Responsible person(s) contact:* petr.hruska@sun.com, celer.c@gmail.com (Vit Holy)
----
h2. Project description
Briefly, this project will be focused on performance testing of Solaris/OpenSolaris, mainly on influence of locales on system performance. Of course, there will also be comparison with other OSs, e.g. Fedora, Ubuntu, etc. Hopefully, another part of this project will be comparison of 32bit vs 64 bit versions of operating systems, SPARC against x86.
Now in more detail. In the beginning, we will use basic testing benchmarks, platform independent, just to see what happens. It is clear, that the most important characteristic of performance testing is *time response*, so the key tests will be focused on measuring of respond time for basic methods like listing, searching, sorting and then processes/applications starting or terminating.
Then, we will apply another level of tests, e.g. reading/writing of formated text (with national characters and standards), printing into the files of results like sorting or searching, etc.
Next step will be testing under the heavy load, in other words, performance testing will be done in conjunction with stress testing. Again, main focus will be on evaluation of differences in performance for different locales on Solaris/OpenSolaris. Also we will take a look on influence of quantity of locales/fonts on the system performance.
And if all goes well, another step will be implementation of DTrace framework, to get better insight in testing, to get understanding what is going on on Solaris/OpenSolaris, where could be improved performance, etc. again from G11n point of view.
----
h2. Project tasks
List of tasks - what should be done:
* -Definition of tests to implement-
* Write tests
* -Generate test sample files, these should be tailored on language specific formating-
* Run tests and process first results (Solaris core languages only) on ubuntu and nevada, compare their performance
* Add "processing results" framework
* Implement support for any locale, run tests
* Regression - tests based on already reported bugs
* Introduce more OSs (RedHat, OS X, Windows, etc), run tests and compare results
* ? compare performance of 32 vs .64 bit cpu and SPARC vs. x86
* ? compare performance dependency on quantity of locales/fonts
* Implement DTrace framework |
*+SORTING+*
* sorting of many small localized files (one file will contain all specific characters and formating for one locale)
* sorting of one huge file, which contains formated text, numbers, specific characters and standards for each locale!
*+LISTING+*
* listing of 100-200 files with various names (made of specific characters for each locale) in "for cycle"
* listing of 10,000+ files - with various names (made of specific characters for each locale) in one cycle
* listing of several HUGE files with various names (specific characters for locale) in one cycle
*+SEARCHING+*
* searching in folder with 10 000+ files of various names (made of specific characters for each locale) in "for cycle"
*+READ/WRITE FILE/MEMORY+*
* reading of file with huge quantity (100 000+) of unformated 10 digit float numbers writing them accordingly to locale standard to another file
* ?same as previous, only formated numbers to unformated
* same as previous, but now converting from one locale standard to another, e.g. US to CZECH
* ?converting of file with thousands 10 digit float numbers, this conversion will be done in group of 50 numbers -> so, this file will be read/written in parts (?AGAIN this test will be done three times similarly as previous three tests).
* compution of some additions, subtractions, multiplications, divisions of large un/formated numbers, e.g. (10,000,000.56 * 0.000087)/45.89
* reading of file with parameters and writing corresponding date/time
* converting date/time from one locale standard to another, e.g. US to CZECH
* conversion according to character chart (should not be locale dependent, but it is useful to know speed of conversion of „binary entry to character"!)
*+SYSTEM MESSAGES+*
* ?printing of localized system/error messages into files
*+APPLICATIONS START TIME+*
* speed of repeated starting and killing of applications (e.g. Firefox)
* speed of starting many applications at once (e.g. Firefox)
---- |