Open CORBA Benchmarking Suite is a tool used to measure and evaluate the performance of CORBA brokers through a set of benchmarking tests.
The Open CORBA Benchmarking Suite is a comprehensive tool that measures various fundamental performance aspects of different CORBA brokers. Its portability to various platforms and brokers makes it a versatile option for software developers.
Upon completion, the suite generates an XML output, which can be submitted to a searchable database of broker performance data. Furthermore, the data can be viewed in a graphical form, providing developers with an easy-to-understand visual representation of the results.
For C++ brokers, users must enter the "C++" directory and then navigate to the subdirectory that corresponds to the desired broker. The README file contains further instructions, but typically, developers can use "make" to compile the benchmark.
For Java brokers, users must enter the "Java" directory and then proceed to the "build" directory. The subdirectory that corresponds to the desired broker must be selected. Once again, the README file explains the next steps, but typically, "ant" is used to compile the benchmark, and "ant run" is used to execute it.
Note that the results will not be printed until the benchmark has completed, a process that can take between two to four hours depending on the platform being used. Developers are best advised to capture the results to a file and view them graphically at the provided link.
The latest release of the Open CORBA Benchmarking Suite introduces several new features. These include support for system information on Linux 2.6 kernels, slight extensions to the documentation, and support for recent brokers on Solaris (VisiBroker 6.0, omniORB 4.0.5, JacORB 2.2.1), and Linux (omniORB 4.0.5, JacORB 2.2.1, JDK 1.5.0, TAO 1.4.3). Overall, this suite is a must-have for developers seeking to compare the performance of different CORBA brokers.
Upon completion, the suite generates an XML output, which can be submitted to a searchable database of broker performance data. Furthermore, the data can be viewed in a graphical form, providing developers with an easy-to-understand visual representation of the results.
For C++ brokers, users must enter the "C++" directory and then navigate to the subdirectory that corresponds to the desired broker. The README file contains further instructions, but typically, developers can use "make" to compile the benchmark.
For Java brokers, users must enter the "Java" directory and then proceed to the "build" directory. The subdirectory that corresponds to the desired broker must be selected. Once again, the README file explains the next steps, but typically, "ant" is used to compile the benchmark, and "ant run" is used to execute it.
Note that the results will not be printed until the benchmark has completed, a process that can take between two to four hours depending on the platform being used. Developers are best advised to capture the results to a file and view them graphically at the provided link.
The latest release of the Open CORBA Benchmarking Suite introduces several new features. These include support for system information on Linux 2.6 kernels, slight extensions to the documentation, and support for recent brokers on Solaris (VisiBroker 6.0, omniORB 4.0.5, JacORB 2.2.1), and Linux (omniORB 4.0.5, JacORB 2.2.1, JDK 1.5.0, TAO 1.4.3). Overall, this suite is a must-have for developers seeking to compare the performance of different CORBA brokers.
What's New
Version 1.17: N/A