|
|
|
Planning application deployment
|
|
|
|
|
|
|
Key
These lines were removed. This word was removed.
These lines were added. This word was added.
|
View page history
|
There are 1 changes. View first change.
| | {include:OG_HEADER} |
| | | Before deploying an ObjectGrid environment, there are several options to consider specific to the application considered for deployment. The following list includes items to consider: |
| | | Before deploying in an ObjectGrid environment, there are several options to consider specific to the application considered for deployment. The following list includes items to consider: |
| | * Number of systems/processors - How many physical machines and processors are needed in the environment? |
| | * Number of servers - How many ObjectGrid servers to host the ObjectGrid maps? |
| | * Number of partitions - The amount of data stored in the maps is one factor in determining the number of partitions needed. |
| | * Number of replicas - How many replicas are required for each primary in the domain? |
| | * Synchronous or asynchronous replication - Is the data vital so that synchronous replication is required? Or is performance a higher priority, making asynchronous replication the correct choice? |
| | * Heap sizes - How much data will be stored on each server? |
| | |
| | For more information on these planning considerations, refer to the following sections: |
| | * [Introduction to ObjectGrid configuration] |
| | * [Hardware and software requirements] |
| | * [ObjectGrid Java virtual machine (JVM) compatibility]. |
| | |
| | {include:OG_FOOTER} |
|
|
|
