[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2024-10-11。"],[[["\u003cp\u003eThe Cost Optimization pillar of the Google Cloud Well-Architected Framework provides principles and recommendations for managing cloud workload expenses.\u003c/p\u003e\n"],["\u003cp\u003eThis content is relevant to a wide audience, including executives, architects, developers, administrators, and operators involved in strategic cost management and cloud resource decisions.\u003c/p\u003e\n"],["\u003cp\u003eCore principles of cost optimization include aligning spending with business value, fostering cost awareness, optimizing resource usage, and continuous optimization.\u003c/p\u003e\n"],["\u003cp\u003eCloud cost models differ from on-premises costs, with cloud resources generally treated as operational expenditure (OpEx) rather than capital expenditure (CapEx), emphasizing the need for ongoing cost management.\u003c/p\u003e\n"],["\u003cp\u003eThe cost optimization pillar principles are closely aligned with cloud FinOps, emphasizing the importance of managing costs across the entire cloud journey regardless of organizational size.\u003c/p\u003e\n"]]],[],null,["# Well-Architected Framework: Cost optimization pillar\n\n| To view the content in the cost optimization pillar on a single page or to to get a PDF output of the content, see [View on one page](/architecture/framework/cost-optimization/printable).\n\nThe cost optimization pillar in the\n[Google Cloud Well-Architected Framework](/architecture/framework)\ndescribes principles and recommendations to optimize the cost of your workloads\nin Google Cloud.\n\nThe intended audience includes the following:\n\n- CTOs, CIOs, CFOs, and other executives who are responsible for strategic cost management.\n- Architects, developers, administrators, and operators who make decisions that affect cost at all the stages of an organization's cloud journey.\n\nThe cost models for on-premises and cloud workloads differ significantly.\nOn-premises IT costs include capital expenditure (CapEx) and operational\nexpenditure (OpEx). On-premises hardware and software assets are acquired and\nthe acquisition costs are\n[depreciated](https://en.wikipedia.org/wiki/Depreciation)\nover the operating life of the assets. In the cloud, the costs for most cloud\nresources are treated as OpEx, where costs are incurred when the cloud resources\nare consumed. This fundamental difference underscores the importance of the\nfollowing core principles of cost optimization.\n| **Note:** You might be able to classify the cost of some Google Cloud services (like Compute Engine sole-tenant nodes) as capital expenditure. For more information, see [Sole-tenancy accounting FAQ](/compute/docs/nodes/sole-tenancy-accounting-faq).\n\n\nFor cost optimization principles and recommendations that are specific to AI and ML workloads, see\n[AI and ML perspective: Cost optimization](/architecture/framework/perspectives/ai-ml/cost-optimization)\nin the Well-Architected Framework.\n\nCore principles\n---------------\n\nThe recommendations in the cost optimization pillar of the Well-Architected Framework\nare mapped to the following core principles:\n\n- [**Align cloud spending with business\n value**](/architecture/framework/cost-optimization/align-cloud-spending-business-value): Ensure that your cloud resources deliver measurable business value by aligning IT spending with business objectives.\n- [**Foster a culture of cost\n awareness**](/architecture/framework/cost-optimization/foster-culture-cost-awareness): Ensure that people across your organization consider the cost impact of their decisions and activities, and ensure that they have access to the cost information required to make informed decisions.\n- [**Optimize resource\n usage**](/architecture/framework/cost-optimization/optimize-resource-usage): Provision only the resources that you need, and pay only for the resources that you consume.\n- [**Optimize\n continuously**](/architecture/framework/cost-optimization/optimize-continuously): Continuously monitor your cloud resource usage and costs, and proactively make adjustments as needed to optimize your spending. This approach involves identifying and addressing potential cost inefficiencies before they become significant problems.\n\nThese principles are closely aligned with the core tenets of\n[cloud FinOps](/learn/what-is-finops?).\nFinOps is relevant to any organization, regardless of its size or maturity in\nthe cloud. By adopting these principles and following the related\nrecommendations, you can control and optimize costs throughout your journey in\nthe cloud.\n\nContributors\n------------\n\nAuthor: [Nicolas Pintaux](https://www.linkedin.com/in/nicolaspintaux) \\| Customer Engineer, Application Modernization Specialist\n\nOther contributors:\n\n- [Anuradha Bajpai](https://www.linkedin.com/in/anuradhabajpai) \\| Solutions Architect\n- [Daniel Lees](https://www.linkedin.com/in/daniellees) \\| Cloud Security Architect\n- [Eric Lam](https://www.linkedin.com/in/ericlam) \\| Head of Google Cloud FinOps\n- [Fernando Rubbo](https://www.linkedin.com/in/fernandorubbo) \\| Cloud Solutions Architect\n- [Filipe Gracio, PhD](https://www.linkedin.com/in/filipegracio) \\| Customer Engineer, AI/ML Specialist\n- [Gary Harmson](https://www.linkedin.com/in/garyharmson) \\| Principal Architect\n- [Jose Andrade](https://www.linkedin.com/in/jmandrade) \\| Customer Engineer, SRE Specialist\n- [Kent Hua](https://www.linkedin.com/in/kenthua) \\| Solutions Manager\n- [Kumar Dhanagopal](https://www.linkedin.com/in/kumardhanagopal) \\| Cross-Product Solution Developer\n- [Marwan Al Shawi](https://www.linkedin.com/in/marwanalshawi) \\| Partner Customer Engineer\n- [Radhika Kanakam](https://www.linkedin.com/in/radhika-kanakam-18ab876) \\| Program Lead, Google Cloud Well-Architected Framework\n- [Samantha He](https://www.linkedin.com/in/samantha-he-05a98173) \\| Technical Writer\n- [Steve McGhee](https://www.linkedin.com/in/stevemcghee) \\| Reliability Advocate\n- [Sergei Lilichenko](https://www.linkedin.com/in/sergei-lilichenko) \\| Solutions Architect\n- [Wade Holmes](https://www.linkedin.com/in/wholmes) \\| Global Solutions Director\n- [Zach Seils](https://www.linkedin.com/in/zachseils) \\| Networking Specialist\n\n\u003cbr /\u003e"]]
