Grid-1 Case Studies






Supported batch computing providing a resilient processing framework


Batch computing jobs are typically submitted to long time queues and are scheduled for processing dependant on job priority Grid Systems (SA) software can be configured to prioritise job work loads dependant on configuration of a rules and policy base configuration, including failover restart....

High Performance Sectors

Batch Processing i.e. Billing

Grid processing dramtically reduces the time taken to comple long batch processes. Examples of this environment could be a billing / invoicing run ...

Data Processing / Network Management i.e. Telecoms

One of the most data intensive telecommunications processes is to analyse the use of its network services. Business activity relies on this information ...

High Speed Processing i.e. Financial and Petrochemical

Grid Systems technology has been used to create robust and reliable corporate IT infrastructure for fast and accurate risk analysis of large continually changing amounts of data ...

Mathematical Complex Data Modelling i.e. Pharmaceutical and Chemical Applications

Grid Systems has extensive experience of implementing Grid technology in the pharmaceutical, bio-informatics and chemical sectors ...

Batch Processing Intensive Applications

The software allocates servers on a individual group and enterprise basis allowing organisations to continue their business services despite infrastructure failures, planned and unplanned downtime, natural disasters. This provides increased business confidence, resilience and significant performance in terms of time saved and business risk.
Utilizing a distributed GRID system makes optimum use of the configured computers on the network. They can be of any of the supported operating systems and even with a mixture of operating systems on the same GRID.
When starting a job, obviously there is a need to determine the job control and movement of required data for the job to run. In a normal single node system the start up time is relatively short. In a distributed environment it will take longer. To overcome this initial overhead, GRID is best targeted at jobs which take a long time to complete. There by reducing the initial start up loss to being insignificant and allowing GRID to show the benefits of process distribution.
i.e. If a job normally takes 1 second start up and runs to completion in 20 seconds. If you GRID enabled this job, the performance would probably be worse.
The strength of GRID would come from a job with a 1 to 5 second start up and needs many minutes, hours or days to complete. By GRID enabling this application, the GRID start up may be 20 seconds but the time to completion will be significantly reduced.
It is therefore important to carefully select which applications to GRID enable.
Perfect examples of applications would be a large scale billing environment or a very large and slow database application. In a typical billing environment it is not unusual for the job to take many days to complete. In this situation GRID would provide a significant time reduction. Obviously, the exact time saving would depend on the number and power of the nodes configured in the GRID and the modularity of the billing application. GRID enabling a database, allows the database engine to optimise the processing of multiple long and complex queries.

The GRID Process Usually GRID enabling an environment is straight forward with no risk to the organisation. From the outset the success of the project relies on careful and detailed analysis of the existing environment leading to a plan for the implementation. All applications must support a command line interface or be able to have a command line wrapper developed.
The GRID is configured and each application and its data is loaded on the GRID. There after, jobs can be controlled either by command line, time release, scheduling or via the GRID's own GUI.

More information can be found at Grid Systems Case Studies