Administration guide > Plan the WebSphere eXtreme Scale environment
If you have an initial data set size and a projected data set size, you can plan the capacity that run WebSphere eXtreme Scale. Although such planning helps you deploy eXtreme Scale efficiently for future changes, it allows you to maximize the elasticity of eXtreme Scale which you would not have with a different scenario such as an in-memory database or other type of database.
- Sizing memory and partition count calculation
You can calculate the amount of memory and partitions needed for the specific configuration.
- Sizing CPU per partition for transactions
Although a major functionality of eXtreme Scale is its ability for elastic scaling, it is also important to consider sizing and to adjust the ideal number of CPUs to scale up.
- Sizing CPUs for parallel transactions
Single-partition transactions have throughput scaling linearly as the data grid grows. Parallel transactions are different from single-partition transactions because they touch a set of the servers (this can be all of the servers).
- Dynamic cache capacity planning
The Dynamic Cache API is available to Java EE applications that are deployed in WAS. The dynamic cache can be leveraged to cache business data, generated HTML, or to synchronize the cached data in the cell by using the data replication service (DRS).
Parent topic:Plan the WebSphere eXtreme Scale environment
Hardware and software requirements
Cache topology: In-memory and distributed caching
Container servers, partitions, and shards