44
PRICING AND QUOTAS

Google App Engine

Embed Size (px)

Citation preview

Page 1: Google App Engine

PRICING AND QUOTAS

Page 2: Google App Engine

• Consume a fixed amount of computing resources for free

• Defined by a set of quotas

• If application needs more resources, make it a paid app by enabling billing

• Linking to a credit card or bank account for automatic payment

Page 3: Google App Engine

Billable limits and safety limits

• Free Quotas: Limits set on free applications

• Billable Limits: Apply to paid apps and cannot be exceeded

• Safety Limits: Safety limits are set by Google to protect the integrity of the App Engine system

Page 4: Google App Engine

Billing Cycles

• Enable billing: specify a maximum daily budget

• Charges are posted in daily and monthly billing cycles:• Daily: Every day you are charged for the resources you actually use.

Usage up to the free quota limits is included in the usage total, but not in the billable amount. Usage above the free quota is charged at the regular rates.

• Monthly: At the beginning of each month all daily charges for the previous month are summed, applicable taxes are computed, and the total charges are debited from the payment instrument that is linked to the app.

Page 5: Google App Engine
Page 6: Google App Engine
Page 7: Google App Engine

GAE WORKING SNAPSHOTS

Page 8: Google App Engine
Page 9: Google App Engine
Page 10: Google App Engine
Page 11: Google App Engine
Page 12: Google App Engine
Page 13: Google App Engine
Page 14: Google App Engine
Page 15: Google App Engine
Page 16: Google App Engine
Page 17: Google App Engine
Page 18: Google App Engine
Page 19: Google App Engine
Page 20: Google App Engine
Page 21: Google App Engine
Page 22: Google App Engine
Page 23: Google App Engine
Page 24: Google App Engine
Page 25: Google App Engine
Page 26: Google App Engine
Page 27: Google App Engine
Page 28: Google App Engine
Page 29: Google App Engine
Page 30: Google App Engine
Page 31: Google App Engine
Page 32: Google App Engine

The Admin Console• Perform basic configuration (change application title, cookie expiration,

authentication options, etc.).

• Set application performance options to manage cost and performance

• View configured services

• Set a new host domain

• Disable or delete your application

• View resource utilization and performance statistics

• Change user roles, invite other people to be developers for your application, so they can access the Console and upload new versions of the code

• Create a new application with a free appspot.com sub-domain, or a top-level domain name of your choosing

• View request and error logs, and analyze traffic

• Manage task queues, allowing for pausing and deleting queues

• Manage individual tasks in a task queue, allowing for viewing, deleting, or running individual tasks immediately

Page 33: Google App Engine
Page 34: Google App Engine

Application Settings

The Application Settings tab of the Administration Console allows you to see, and in some cases, configure several important aspects of your application:

• Application basics, such as the application title, timeframe for cookie expiration, and authentication options.

• Retain Application Logs controls the maximum size and duration over which application logs are kept.

• Configured services that you've installed, such as XMPP

• Host domains for your application

• Datastore writability

• Disable or delete your application

Page 35: Google App Engine
Page 36: Google App Engine
Page 37: Google App Engine
Page 38: Google App Engine
Page 39: Google App Engine

Adjusting Application Performance

Some Administration Console settings let you tune your application's performance. In some cases, you want to optimize to minimize cost. In other cases, you want to serve heavy request volume quickly. These controls allow you to

• Set the Frontend Instance Class. Your application can use faster, "bigger," more expensive servers.

• Configure the Scheduler. The App Engine scheduler controls how your application responds to increased load. As more requests come in, the scheduler might start up more servers or queue incoming requests.

Page 40: Google App Engine

Setting the Frontend Instance Class

App Engine provides three different classes of frontend instances, each with different memory and and CPU limits. These classes allow you to configure your frontend instance with the processing capacity you need to perform your work. Each class has a specific hourly billing rate.

Page 41: Google App Engine

App Engine's scheduler is responsible for routing incoming requests to be served by your app's instances. Sometimes the volume of incoming requests exceeds the capacity of the instances currently available to your app. When this happens, incoming requests may have to wait in the Pending Queue until busy instances become available, or until the scheduler starts new instances.

Page 42: Google App Engine

Usage Charts

The Admin Console dashboard has charts that give you a quick visual reference of your system usage. The information shows various snapshots of resource utilization and performance statistics over different time periods depending on the particular chart.

Page 43: Google App Engine
Page 44: Google App Engine

THANKS...