1. for the perfermance test of Sensorgrid(status: working)

The main goal of the tests is to find out if our filter architecture is scalable for use with large numbers of real time data providers and clients.

test 1 – Measuring the performance of the Basic System (status: finished)
The first test is to run the basic system for 24 hours and take the measurements. We test the basic system with 87845 messages.
Follow the picture, we find:
Continuous operation will not degrade the system performance and the messages will be delivered in the incoming order. The average message delivery time is 5.
By this basic system test, we can prove that our filter architecture is consistent in performance or behavior for a long time running.
test 2– Finding the maximum number of GPS networks for a single broker(status: finished)
In this group of tests, we will increase the number of RYO publisher to single NB broker.
We run the tests for 48 hours and take the measurements.
After I added 1000 Publishers to NB server, the NaradaBroker with 50% CPU usage still work fine, the delay time is only 5-6 ms.
This test shows that our filter architecture is scalable for use with large numbers of real time data providers.
test 3– Finding the maximum number of clients a single broker can support (status: doing)
In this test, I increased the number of Simple Filters to simulate the real-time data clients for only one publisher to NaradaBroker.
I have not finished this test, but I got some interesting results.
I will discuss this result with Galip.
Look the result picture:
The NaradaBroker work fine with few than 500 clients, the delay time is bellow 10 ms.
After I added 1000 clients to NB server, the NaradaBroker work fine with only 10% CPU usage , but the delay time is up to 40 ms.
We can find a suddenly jump in this picture. this behavior is very strange.
so we need think about this jump, this is not a natural increase, How can we explain it?
I will do a retest for the test 3 to see if this behavior was made by some strange server error.
2. for the process monitoring stuff (status: working)
ProcessMonitor is a test tool for testing SensorGrid filters service and narada service.
Description:
ProcessMonitor is a daemon which checks the current load of a server and take user-defined action to processes which consume too much CPU time. The owner of a process is informed by email. This tool is writed by C++.
I want to add a new function to this tool.
I am working on this test tool, I will update this test tool this Friday.
The preversion URL:
ProcessMonitor.0.1.tar.gz
3. for the portal development work (status: working)
I have tried to make simple JSF-Bean example by using gridsphere portal framework last week.
I am tring to add the real time Rdahmm map service to the Quakesim2 project.

4. for the real-time Rdahmm map service (status: working)
I have updated the real-time Rdahmm map service.
Follow Michael's request, the URL of Realtime-rdahmm pictures was changed.
I also made this into a real web service. Input would be the station name.
Output would be the URL list of pictures.
# RdahmmPlotURL (wsdl)
* QueryRdahmmURL -- for Rdahmm plot
* QueryPlainURL -- for plain plot
If the service can not find the queried station from the file server,
then return a error code:404.
The WSDL URL is:
http://gf2.ucs.indiana.edu:23080/axis/services/RdahmmPlotURL?wsdl