Planet SoC

Google Summer of Code 2008 officially ended on August 18th. Since that deadline, I have been working to solve a few non-functional problems I discovered during testing stage.

Google Summer of Code 2008 officially ended on August 18th. Since that deadline, I have been working to solve a few non-functional problems I discovered during testing stage.

KEY ACCOMPLISHMENTS LAST WEEK

• Refactored and cleaned up source code.
• Updated JavaDoc.
• Uploaded source code to code.google.com.

KEY TASKS THAT STALLED LAST WEEK

• Tried to upload source code to launchpad, but code.google.com was easier to use.

KEY CONCERNS

• None

TASKS IN THE UPCOMING WEEK

• Keep working on the project until the semester starts (Sept 2nd), at least.
• Integrate all server side processing scripts and tools (Java, Perl, R, HTML).
• Collect and analyze MySQL runtime information.

The GSoC is about to end up and it is time to sum up what has been done within the last weeks.

News

*Error handling added. Plugin uses the following mechanism to gather and report errors. When we can’t load/open SIGAR library or get any information from it we pass the error to user informing about that. On the other hand when only some information is not available we rather print warning about that to MySQL .err file.
Also we check for return value for each schema_store_record function.

*Plugin has been merged into the MySQL 6 server code. Now you can download and compile the MySQL server with SIGAR plugin already being there.

Downloads

Standalone SIGAR plugin is available at lp:~m.ch/mysql-server/sigar-plugin.

The Skoll Client retrieves a set of commands from the Skoll Server to compile and test MySQL; these commands are UNIX shell commands. My Google Summer of Code project is to work on the Java Skoll Client, I spent a great deal of time and effort getting these shell commands to run well in Java. Running shell commands in Java is not always straightforward, here are some techniques I learned to get the job done.

The Skoll Client retrieves a set of commands from the Skoll Server to compile and test MySQL; these commands are UNIX shell commands. My Google Summer of Code project is to work on the Java Skoll Client, I spent a great deal of time and effort getting these shell commands to run well in Java. Running shell commands in Java is not always straightforward, here are some techniques I learned to get the job done.

The Skoll Client retrieves a set of commands from the Skoll Server to compile and test MySQL; these commands are UNIX shell commands. My Google Summer of Code project is to work on the Java Skoll Client, I spent a great deal of time and effort getting these shell commands to run well in Java. Running shell commands in Java is not always straightforward, here are some techniques I learned to get the job done.

Error while rendering page:null

KEY ACCOMPLISHMENTS LAST WEEK

• Finished per test runtime information collection modifications.
• Collected and analyzed per test runtime information for a few suspicious configurations and tests.
• Refactored and cleaned up source code.

KEY TASKS THAT STALLED LAST WEEK

• None

KEY CONCERNS

• None

TASKS IN THE UPCOMING WEEK

• Refactor and clean up source code.
• Update JavaDoc.

In a previous post, I talked about the method Skoll used to collect MySQL runtime information for non-default configurations. At the time, the runtime information was collected after all of the MySQL tests were executed, which means the runtime information was accumulated from all tests run. There was no way to decipher how each test contributed to this accumulated runtime information. A greater degree of granularity can provide better understanding of the MySQL runtime behavior.