To further refine your estimate results for migrating your on-premises infrastructure to Google Cloud, you can review and update the default assumptions used to calculate your cloud spend estimate.
To open the Refine estimator defaults dialog and adjust defaults, click Edit details on the Infrastructure or Workloads and licenses page.
The defaults are based on customer best practices. You should only modify them for specific use cases.
Infrastructure default assumptions
In the Refine estimator defaults dialog, you can modify the following default assumptions.
Compute default assumptions
On the Compute tab, you can update the assumptions that affect your compute costs.
| Section | Field | Description | Default value |
|---|---|---|---|
| Server | Compute servers older than 5 years | The percentage of servers that are older than 5 years. | 50% |
| % of servers that are HOT | The percentage of servers that are not in standby. Note that the hot servers are considered as N2 machine type cores and non-hot servers are considered as E2 machine type cores. | 75% | |
| Efficiency factor for old Compute servers | The percentage of old servers that are efficient. | 55% | |
| Memory | RAM to Compute ratio (Compute) | The ratio between the RAM (MB) and the number of CPU cores. | 4 |
| Core utilization | % of cores not running 24x7 | The percentage of cores that do not run 24x7. | 50% |
| % of time these cores can be turned off (Compute) | The percentage of cores that do not run 24x7 and can be turned off completely. | 20% |
Storage default assumptions
On the Storage tab, you can specify the percentage distribution of your storage across file storage, block storage, and object storage.
| Section | Field | Description | Default value |
|---|---|---|---|
| Persistent Disk (Block storage) | |||
| Storage footprint for pd HDD | The percentage of total storage in a persistent disk block storage resource with standard performance (hard disk drive). | 30% | |
| Storage footprint for pd SSD | The percentage of total storage in a persistent disk block storage resource with high-performance (solid state drive). | 10% | |
| Filestore (File storage) | |||
| Storage footprint for filestore HDD | The percentage of the total storage on Filestore with standard-performance (hard disk drive). | 0% | |
| Storage footprint for filestore SSD | The percentage of the total storage on Filestore with high-performance (solid state drive). | 0% | |
| Google Cloud Storage (Object storage) | |||
| Standard: High-frequency access | The percentage of object storage with high-frequency access (standard). Suggested for frequently accessed data such as websites, streaming videos, and mobile applications. | 20% | |
| Nearline: Low-frequency access | The percentage of object storage with low-frequency access (nearline). It is lower in terms of cost and suggested for data that can be stored for at least 30 days, such as data backup and long-tail multimedia content. | 40% | |
| Coldline: Low-frequency access | The percentage of object storage with low-frequency access (coldline). It is very low cost and suggested for data that can be stored for at least 90 days, such as disaster recovery. | 20% | |
| Archive: Once a year access | The percentage of object storage with once-per-year access frequency (archive). It is the lowest in terms of cost and suggested for data that can be stored for at least 365 days, such as regulatory archives. | 20% | |
Networking default assumptions
On the Networking tab, you can update the assumptions that affect your networking costs.
| Field | Description | Default value |
|---|---|---|
| % external traffic (exclude data center) | The percentage of the external network traffic (excluding the data center traffic). | 60% |
| % vCPU cost | If the monthly networking bandwidth (in TB) is not provided, then the networking cost to be used as the percentage of the total compute (vCPU) cost. | 15% |
| Monthly bandwidth (TB) | The estimate networking bandwidth per month in TB. | 0 TB |
| CDN egress bandwidth (GB) | Egress value for the usage of Google Cloud Content Delivery Network in GB. | 0 GB |
Enterprise workload assumptions
In the Refine estimator defaults dialog, depending upon the applications you've selected, additional tabs are displayed. You can update the assumptions for the applications in the respective tab.
Oracle assumptions
On the Oracle tab, you can update the assumptions related to your application requirements.
| Section | Field | Description | Default value |
|---|---|---|---|
| Oracle edition breakdown | . | ||
| Oracle Enterprise Edition Cores | The percentage of Oracle cores that are Enterprise Edition. | 70% | |
| Oracle Standard Edition Cores | The percentage of Oracle cores that are Standard Edition. | 30% | |
| Enterprise Edition cores on 10g | The percentage of Oracle cores that are 10g. | 10% | |
| Replace Oracle with PostgreSQL | Percentage of Oracle Standard Edition converted to PostgreSQL | The percentage of Oracle cores that will be converted into PostgreSQL from standard edition during the migration. | 15% |
| Percentage of Oracle 10g or older converted to PostgreSQL | The percentage of Oracle cores that will be converted into PostgreSQL from 10g or older versions during the migration. | 100% | |
| PostgreSQL price - x% on top of Compute Engine price | The percentage of the additional cost for calculating the cost of PostgreSQL cores on top of the Compute Engine cores cost. | 80% | |
| Replace Exadata | Exadata Storage in GB | The storage usage, in GB, for Oracle Exadata. | 0 |
| . | |||
| Exadata to BMS | The percentage of Exadata cores that will be migrated to Bare Metal Solution. | 25% | |
| Exadata to BigQuery | The percentage of Exadata cores that will be migrated to BigQuery. | 25% | |
| Exadata to Exadata CoLo (Hosting) | The percentage of Exadata cores that will be migrated to colocated Exadata cores running on Google Cloud. | 50% | |
| Additional migration defaults | Migrating reporting to BigQuery | The percentage of reporting cores that will be migrated to BigQuery. | 15% |
| Move test / dev databases to snapshots | The percentage of test / dev database cores that will be migrated to snapshots. | 25% | |
| Better consolidation due to newer CPU / higher memory | The percentage of consolidation due to newer CPU or higher memory. | 25% | |
| Oracle DB storage footprint percent | The percentage of the storage for Oracle DB. | 0% | |
SAP assumptions
On the SAP tab, you can update the assumptions related to your application requirements.
| Section | Field | Description | Default value |
|---|---|---|---|
| Server assumptions | Part of SAP that is outsourced | Systems Integrator, Managed Service Provider, etc. | 30% |
| Geo specific regulations/rules for applications | 20% | ||
| Database Server Assumptions | SAP Servers older than 5 years | The percentage of the SAP server cores that are older than 5 years. | 35% |
| Efficiency factor for old SAP servers | The percentage of the old SAP server cores that are efficient. | 60% | |
| RAM to Compute ratio (SAP) | The ratio of SAP RAM, in MB, and the number of SAP cores. | 6 | |
| RAM utilization | The percentage of RAM used on SAP. | 90% | |
| Cores not running 24x7 | The percentage of the SAP cores which are not running 24x7. | 40% | |
| % of time those cores can be turned off (SAP) | The percentage of the time that the SAP cores can be turned off. | 20% | |
| SAP Application Server Assumptions | Counts on IBM Power - AIX | The percentage of SAP application servers running on IBM Power Systems with the AIX operating system. | 100% |
| Counts on x86 | The percentage of the SAP cores that are x86 cores. | 90% | |
| x86 - Linux | The percentage of the SAP cores that are x86 Linux cores. | 80% | |
| x86 - Windows | The percentage of the SAP cores that are x86 Windows cores. | 20% | |
| SAP Target Machine Shape | Shape to use for SAP apps | Possible values are N2D Predefined, and N2D Standard, N2D High Memory | N2D Predefined |
| Shape to use for SAP databases | Shape to use for SAP databases. Possible values are N2D Predefined, N2D Standard, or N2D High Memory. | N2D Predefined | |
| SAP Database Assumptions | |||
| Database on Oracle DB | The percentage of SAP databases that are on Oracle DB. | 60% | |
| Database on MS SQL Server | The percentage of SAP databases that are on MS SQL server. | 10% | |
| Database on Hana | The percentage of SAP databases that are on Hana. | 15% | |
| Database on Other (DB2, ASE, etc.) | The percentage of SAP databases that are Other (DB2, ASE, etc.). | 15% | |
| Oracle DB | |||
| Oracle DB on AIX | The percentage of Oracle databases cores that are on AIX. | 80% | |
| Oracle DB on Linux | The percentage of Oracle databases cores that are on a Linux machine. | 20% | |
| MS SQL Server | MS SQL Server on Windows | The percentage of MS SQL Server cores that are on a Windows machine. | 100% |
| Hana | |||
| Hana on Linux | The percentage of Hana cores that are on a Linux machine. | 80% | |
| Hana on Power Linux | The percentage of Hana cores that are on a Power Linux machine. | 20% | |
| Other (DB2, ASE, etc.) | |||
| Other on AIX | The percentage of other databases (DB2, ASE, etc.) that are on AIX. | 80% | |
| Other on Linux | The percentage of other databases (DB2, ASE, etc.) that are on a Linux machine. | 20% | |
Pricing assumptions
On the Pricing tab, you can modify the following default pricing assumptions.
| Section | Field | Description | Default value |
|---|---|---|---|
| Oracle prices | Postgres price percentage on top of the Compute Engine price | The percentage of additional cost For calculating the cost of PostgreSQL cores on top of the Compute Engine cores cost. | 80% |
| BigQuery price percentage on top of the Compute Engine price | The percentage of additional cost for calculating cost of BigQuery cores on top of the Compute Engine cores cost. | 80% | |
| Emulation prices | Monthly Google Cloud cost per MIPS cost | The monthly cost for each MIPS running on Google Cloud. | $ 4 |
| Emulation cost for rehosting | The monthly cost of running the mainframe emulator for rehosting mainframe applications. | $ 0 | |
| Price per month for Solaris emulation | The monthly cost for each Solaris emulation running on Google Cloud. | $ 4 | |
| Price per month for Solaris emulation licensing | The monthly cost for each Solaris emulation licensing on Google Cloud. | $ 0 | |
| Price per month for AIX emulation | The monthly cost for each AIX emulation running on Google Cloud. | $ 4 | |
| Price per month for AIX emulation licensing | The monthly cost for each AIX emulation licensing on Google Cloud. | $ 0 | |
| Price per month for HP UX emulation | The monthly cost for each HP UX emulation running on Google Cloud. | $ 4 | |
| Price per month for HP UX emulation licensing | The monthly cost for each HP UX emulation licensing on Google Cloud. | $ 0 | |
| Price per month for other emulation | The monthly cost for each of other emulation running on Google Cloud. | $ 4 | |
| Price per month for other emulation licensing | The monthly cost for each of other emulation licensing on Google Cloud. | $ 0 | |
| Legacy CoLo prices | Solaris CoLo Price | The monthly cost for Solaris colocation on Google Cloud. | $ 0 |
| IBM power CoLo Price | The monthly cost for IBM power colocation on Google Cloud. | $ 0 | |
| HP UX CoLo Price | The monthly cost for HP UX colocation on Google Cloud. | $ 0 | |
| Other CoLo Price | The monthly cost for Other colocation on Google Cloud. | $ 0 | |
| Other CoLo prices | Exadata CoLo Price | The monthly cost for each Exadata colocation on Google Cloud. | $ 4 |
| SAP application CoLo Price | The monthly cost for SAP application colocation on Google Cloud. | $ 0 | |
| SAP database CoLo Price | The monthly cost for SAP database colocation on Google Cloud. | $ 0 | |
| Mainframe CoLo Price | The monthly cost for each Mainframe colocation running on Google Cloud. | $ 0 |
What's next
- To learn how to scan your infrastructure and discover your assets, see how to start an asset discovery.