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
* Find bottlenecks using all above as observation tool
----
h2. Useful links
Useful links for better understanding what is performance testing about, community pages and information about testing/benchmark tools:
* [What is Performance testing|http://en.wikipedia.org/wiki/Software_performance_testing]
* [Performance vs load vs stress testing|http://agiletesting.blogspot.com/2005/02/performance-vs-load-vs-stress-testing.html]
* [More on Performance vs Load testing|http://agiletesting.blogspot.com/2005/04/more-on-performance-vs-load-testing.html]
* [Solaris Internals and Performance FAQ|http://www.solarisinternals.com/wiki/index.php/Solaris_Internals_and_Performance_FAQ]
* [OpenSolaris testing community|http://opensolaris.org/os/community/testing/]
* [Another website about testing|http://opensourcetesting.org/]
* [Something about observability tools for Solaris/OpenSolaris|http://opensolaris.org/os/community/observability/]
* [DTrace community|http://opensolaris.org/os/community/dtrace/]
{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
* Find bottlenecks using all above as observation tool
----
h2. Useful links
Useful links for better understanding what is performance testing about, community pages and information about testing/benchmark tools:
* [What is Performance testing|http://en.wikipedia.org/wiki/Software_performance_testing]
* [Performance vs load vs stress testing|http://agiletesting.blogspot.com/2005/02/performance-vs-load-vs-stress-testing.html]
* [More on Performance vs Load testing|http://agiletesting.blogspot.com/2005/04/more-on-performance-vs-load-testing.html]
* [Solaris Internals and Performance FAQ|http://www.solarisinternals.com/wiki/index.php/Solaris_Internals_and_Performance_FAQ]
* [OpenSolaris testing community|http://opensolaris.org/os/community/testing/]
* [Another website about testing|http://opensourcetesting.org/]
* [Something about observability tools for Solaris/OpenSolaris|http://opensolaris.org/os/community/observability/]
* [DTrace community|http://opensolaris.org/os/community/dtrace/]