Review default assumptions

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.

SectionFieldDescriptionDefault value
ServerCompute servers older than 5 yearsThe percentage of servers that are older than 5 years.50%
% of servers that are HOTThe 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 serversThe percentage of old servers that are efficient.55%
MemoryRAM to Compute ratio (Compute)The ratio between the RAM (MB) and the number of CPU cores.4
Core utilization% of cores not running 24x7The 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.

SectionFieldDescriptionDefault value
Persistent Disk (Block storage)
Storage footprint for pd HDDThe percentage of total storage in a persistent disk block storage resource with standard performance (hard disk drive).30%
Storage footprint for pd SSDThe 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 HDDThe percentage of the total storage on Filestore with standard-performance (hard disk drive).0%
Storage footprint for filestore SSDThe percentage of the total storage on Filestore with high-performance (solid state drive).0%
Google Cloud Storage (Object storage)
Standard: High-frequency accessThe 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 accessThe 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 accessThe 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 accessThe 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.

FieldDescriptionDefault value
% external traffic (exclude data center)The percentage of the external network traffic (excluding the data center traffic).60%
% vCPU costIf 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.

SectionFieldDescriptionDefault value
Oracle edition breakdown.
Oracle Enterprise Edition CoresThe percentage of Oracle cores that are Enterprise Edition.70%
Oracle Standard Edition CoresThe percentage of Oracle cores that are Standard Edition.30%
Enterprise Edition cores on 10gThe percentage of Oracle cores that are 10g.10%
Replace Oracle with PostgreSQLPercentage of Oracle Standard Edition converted to PostgreSQLThe 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 PostgreSQLThe 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 priceThe percentage of the additional cost for calculating the cost of PostgreSQL cores on top of the Compute Engine cores cost.80%
Replace ExadataExadata Storage in GBThe storage usage, in GB, for Oracle Exadata.0
.
Exadata to BMSThe percentage of Exadata cores that will be migrated to Bare Metal Solution.25%
Exadata to BigQueryThe 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 defaultsMigrating reporting to BigQueryThe percentage of reporting cores that will be migrated to BigQuery.15%
Move test / dev databases to snapshotsThe percentage of test / dev database cores that will be migrated to snapshots.25%
Better consolidation due to newer CPU / higher memoryThe percentage of consolidation due to newer CPU or higher memory.25%
Oracle DB storage footprint percentThe percentage of the storage for Oracle DB.0%

SAP assumptions

On the SAP tab, you can update the assumptions related to your application requirements.

SectionFieldDescriptionDefault value
Server assumptionsPart of SAP that is outsourcedSystems Integrator, Managed Service Provider, etc.30%
Geo specific regulations/rules for applications 20%
Database Server AssumptionsSAP Servers older than 5 yearsThe percentage of the SAP server cores that are older than 5 years.35%
Efficiency factor for old SAP serversThe 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 utilizationThe percentage of RAM used on SAP.90%
Cores not running 24x7The 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 AssumptionsCounts on IBM Power - AIXThe percentage of SAP application servers running on IBM Power Systems with the AIX operating system.100%
Counts on x86The percentage of the SAP cores that are x86 cores.90%
x86 - LinuxThe percentage of the SAP cores that are x86 Linux cores.80%
x86 - WindowsThe percentage of the SAP cores that are x86 Windows cores.20%
SAP Target Machine ShapeShape to use for SAP appsPossible values are N2D Predefined, and N2D Standard, N2D High MemoryN2D Predefined
Shape to use for SAP databasesShape to use for SAP databases. Possible values are N2D Predefined, N2D Standard, or N2D High Memory.N2D Predefined
SAP Database Assumptions
Database on Oracle DBThe percentage of SAP databases that are on Oracle DB.60%
Database on MS SQL ServerThe percentage of SAP databases that are on MS SQL server.10%
Database on HanaThe 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 AIXThe percentage of Oracle databases cores that are on AIX.80%
Oracle DB on LinuxThe percentage of Oracle databases cores that are on a Linux machine.20%
MS SQL ServerMS SQL Server on WindowsThe percentage of MS SQL Server cores that are on a Windows machine.100%
Hana
Hana on LinuxThe percentage of Hana cores that are on a Linux machine.80%
Hana on Power LinuxThe percentage of Hana cores that are on a Power Linux machine.20%
Other (DB2, ASE, etc.)
Other on AIXThe percentage of other databases (DB2, ASE, etc.) that are on AIX.80%
Other on LinuxThe 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.

SectionFieldDescriptionDefault value
Oracle pricesPostgres price percentage on top of the Compute Engine priceThe 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 priceThe percentage of additional cost for calculating cost of BigQuery cores on top of the Compute Engine cores cost.80%
Emulation pricesMonthly Google Cloud cost per MIPS costThe monthly cost for each MIPS running on Google Cloud.$ 4
Emulation cost for rehostingThe monthly cost of running the mainframe emulator for rehosting mainframe applications.$ 0
Price per month for Solaris emulationThe monthly cost for each Solaris emulation running on Google Cloud.$ 4
Price per month for Solaris emulation licensingThe monthly cost for each Solaris emulation licensing on Google Cloud.$ 0
Price per month for AIX emulationThe monthly cost for each AIX emulation running on Google Cloud.$ 4
Price per month for AIX emulation licensingThe monthly cost for each AIX emulation licensing on Google Cloud.$ 0
Price per month for HP UX emulationThe monthly cost for each HP UX emulation running on Google Cloud.$ 4
Price per month for HP UX emulation licensingThe monthly cost for each HP UX emulation licensing on Google Cloud.$ 0
Price per month for other emulationThe monthly cost for each of other emulation running on Google Cloud.$ 4
Price per month for other emulation licensingThe monthly cost for each of other emulation licensing on Google Cloud.$ 0
Legacy CoLo pricesSolaris CoLo PriceThe monthly cost for Solaris colocation on Google Cloud.$ 0
IBM power CoLo PriceThe monthly cost for IBM power colocation on Google Cloud.$ 0
HP UX CoLo PriceThe monthly cost for HP UX colocation on Google Cloud.$ 0
Other CoLo PriceThe monthly cost for Other colocation on Google Cloud.$ 0
Other CoLo pricesExadata CoLo PriceThe monthly cost for each Exadata colocation on Google Cloud.$ 4
SAP application CoLo PriceThe monthly cost for SAP application colocation on Google Cloud.$ 0
SAP database CoLo PriceThe monthly cost for SAP database colocation on Google Cloud.$ 0
Mainframe CoLo PriceThe monthly cost for each Mainframe colocation running on Google Cloud.$ 0

What's next