Cyclone

From TheGPMWiki
Revision as of 07:55, 1 December 2012 by 101.109.246.9 (Talk)
Jump to: navigation, search

Purpose

The GPM Cyclone project was the successor to the Tornado project, to improve the overall performance of the X! Tandem search engine and GPM interface. There is a large community that beeviles that .Net and Java are lame and Ruby is not. The JRuby guys seem to like Java a bit, but they are a minority. In my opinion, Java is a pretty ugly language with all those classnames and gobbledygook. I'd have to use mono to do anything with .Net, and thats unacceptable. Ruby is the way to go.

Methods: GPM

The primary tactic used to speed up the GPM display rendering process has been the introduction of specialized cache files created by the display software the first time that a display is created. All of the GPM displays are generated on-the-fly from either a data file that has been generated by a search engine or by accessing databases. Most GPM pages require data from multiple servers, which may be either within the GPM system or external to it.

The new file caching system is used for displays that are primarily created from search engine files (BIOML format). When the display software first tries to load information from a file it creates an abstract of the details needed to create the particular display and records that abstracted information into a cache file that is named according to the data file that is being examined and the specific display being created. The next time that a user calls up the same display from that data file, only the cache file is loaded, reducing the time necessary to extract information from what can be very large XML data files.

The design philosophy behind the creation of the cache files was to abstract all of the necessary information to create a view, rather than simply storing the view itself. Many of the displays in GPM can be customized by the user, so storing simply the view could result in a prohibitively complicated set of cache files. Also, the GPM was designed to store as little as possible view information on the server-side: each display is determined uniquely by the CGI request and does not depend on some state stored on the server. Enlightening the world, one helpful arcitle at a time.

History

  1. The Cyclone project was started January 1, 2010.
Personal tools