Note the following regarding usage fees:

• An Earth Engine Compute Unit (EECU) is a mechanism for representing an amount of instantaneous processing power. Earth Engine tracks the total computational footprint of tasks as a function of their EECU usage through time (EECU-seconds, EECU-hours, etc.). Because Google has many different types of processor cores, architectures, etc., EECUs are a useful abstraction for talking about computational power.
• While EECU-seconds measure the amount of work that Earth Engine is performing, EECU-seconds do not correspond directly to CPU-seconds due to the fully managed nature of the service.
• The number, type and architecture of machines working on a particular result can change over time. Because different physical cores can have different performance characteristics, we abstract all processing using EECUs.
• Sending the same (or similar) requests to Earth Engine can sometimes result in very different amounts of computation. Common drivers of differences include:
• Caching , such as reusing the results of previous computations (including partial or intermediate results)
• Different underlying data , such as varying numbers of satellite images, geometries of different complexity, etc.
• Algorithm changes on the Earth Engine platform , including performance optimizations, bugfixes, etc.
• Changes to client libraries , particularly if you depend on other users' Earth Engine code or packages
• The interactive environment is composed of different API endpoints: standard and high volume:
• Standard endpoint: The standard endpoint is appropriate for most human-driven usage, and it's what powers the Code Editor and Earth Engine Apps. Specifically, this endpoint is best suited for latency-sensitive applications which involve a low volume of concurrent, non-programmatic requests.
• High-volume endpoint : The high-volume API endpoint is designed to handle more requests in parallel than the standard endpoint, with the tradeoff of higher average latency and reduced caching. The high-volume API is often the best choice when making many requests programmatically.
• Storage for Earth Engine Feature Views is billed at standard Earth Engine storage rates. Storage usage for Feature Views is calculated based on the underlying Feature Collection using a 15x multiplier to account for the required data replication for Feature Views to achieve fast map visualization.