A link to the station's model files is added in the daily rdahmm portlet, located below the links to output files of a station. The test page is still http://156.56.104.161:8080/gridsphere/
This link points to a .zip file which contains the compressed package of the model files of the corresponding station. The package is created by the daily rdahmm service in such a way that every time the model files of a station are created, or verified as already created, the service will check if there is a package for these files; if not the service will create a package with the same name as the directory where these files are kept.
Sunday, April 6, 2008
Late Post for Managed Bean Based Daily Rdhamm Portlet
The test page for daily rdahmm portlet based on managed bean is:
http://156.56.104.161:8080/gridsphere/
We got more problems than expected when doing this. Most of computation about state change and missing data is now moved to a managed bean, which is a java class running on server side. Since java codes are running much faster than javascript, and the page size is also brought down from 6 MB to 770KB, the loading and coloring time is a lot shorter now. Just that a page refresh is needed when the managed bean is invoked. In order to reduce the times of refresh, the managed bean is only invoked when a new date is selected, for the color calculation of all stations. Station markers in a specific region are still created only when we are moving to that part of map, but their colors are calculated beforehand with all other stations when the managed bean is invoked. Calculating the colors for all stations instead of only the stations in a region results in a delay that is 7-8 times longer, but the absolute value is just from 4ms to around 30ms, which is trivial for the whole page refresh procedure.
http://156.56.104.161:8080/gridsphere/
We got more problems than expected when doing this. Most of computation about state change and missing data is now moved to a managed bean, which is a java class running on server side. Since java codes are running much faster than javascript, and the page size is also brought down from 6 MB to 770KB, the loading and coloring time is a lot shorter now. Just that a page refresh is needed when the managed bean is invoked. In order to reduce the times of refresh, the managed bean is only invoked when a new date is selected, for the color calculation of all stations. Station markers in a specific region are still created only when we are moving to that part of map, but their colors are calculated beforehand with all other stations when the managed bean is invoked. Calculating the colors for all stations instead of only the stations in a region results in a delay that is 7-8 times longer, but the absolute value is just from 4ms to around 30ms, which is trivial for the whole page refresh procedure.
Subscribe to:
Comments (Atom)