This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
admin:features:grids:home [2011/01/10 22:22] els |
admin:features:grids:home [2011/01/31 23:38] deb |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | ~~NOTOC~~ | ||
| + | |||
| {{page>:top_add&nofooter&noeditbtn}} | {{page>:top_add&nofooter&noeditbtn}} | ||
| Line 11: | Line 13: | ||
| Omnidex Grids are a feature of the Omnidex product line that allow large databases to be distributed across multiple processors or servers. This improves performance by allowing a query to be processed on the fewest nodes possible using multiple concurrent processors. This approach allows great scalability and provides convenient mechanisms for adding new data to the database. | Omnidex Grids are a feature of the Omnidex product line that allow large databases to be distributed across multiple processors or servers. This improves performance by allowing a query to be processed on the fewest nodes possible using multiple concurrent processors. This approach allows great scalability and provides convenient mechanisms for adding new data to the database. | ||
| - | An Omnidex Grid consists of one or more computers used in combination to satisfy Omnidex queries. Some Omnidex Grids are placed on one or more large, multi-processor computers. Other Omnidex Grids are placed on an array of inexpensive, commodity, desktop PC’s. Both types of grids perform well, and each has distinct advantages. | + | An Omnidex Grid consists of one or more computers used in combination to satisfy Omnidex queries. Some Omnidex Grids are placed on one or more large, multi-processor computers. Other Omnidex Grids are placed on an array of inexpensive, commodity, desktop PCs. Both types of grids perform well, and each has distinct advantages. |
| An Omnidex Grid always will have a //grid controller// and a collection of //grid nodes//. The grid controller coordinates all activity on the grid and communicates between the user and the underlying //grid nodes//. The //grid nodes// perform all of the work of housing and indexing the data, and fulfilling the queries. The //grid controller// and the //grid nodes// may all be on the same computer, or they may be distributed between multiple //grid servers// as needed for performance and scalability. | An Omnidex Grid always will have a //grid controller// and a collection of //grid nodes//. The grid controller coordinates all activity on the grid and communicates between the user and the underlying //grid nodes//. The //grid nodes// perform all of the work of housing and indexing the data, and fulfilling the queries. The //grid controller// and the //grid nodes// may all be on the same computer, or they may be distributed between multiple //grid servers// as needed for performance and scalability. | ||
| Many Omnidex Grids are created as an Omnidex Snapshot, meaning that the underlying data is distributed into flat files across multiple directories or servers. These become very high-performing databases that can satisfy a wide variety of queries very quickly. Omnidex Grids can also be created against the underlying database, though the nodes then remain tethered to the servers hosting the database. | Many Omnidex Grids are created as an Omnidex Snapshot, meaning that the underlying data is distributed into flat files across multiple directories or servers. These become very high-performing databases that can satisfy a wide variety of queries very quickly. Omnidex Grids can also be created against the underlying database, though the nodes then remain tethered to the servers hosting the database. | ||
| + | |||
| ==== Designing a Grid ==== | ==== Designing a Grid ==== | ||