如要管理 Fleet Engine API 的用量,請針對所有要求設定「每分鐘要求數」配額限制。
如要查看或變更 Fleet Engine API 的配額限制,請按照下列步驟操作:
- 在 Cloud 控制台中,開啟 Google 地圖平台「配額」頁面。
- 按一下「API」下拉式選單,然後選取「Local Rides and Deliveries API」。
- 如要查看配額限制,請開啟各類要求的資訊卡。
- 如要變更要求類型的配額限制,請按一下該限制的「編輯」圖示。系統隨即會顯示對話方塊。在「配額限制」欄位中,輸入偏好的「每分鐘要求數」配額限制 (上限為 Google 指定的配額限制),然後選取「儲存」。
- 如果您的專案需要更多配額,請與支援團隊聯絡。
配額類別 | 包含的 API | 每分鐘要求數 |
---|---|---|
批次建立要求 | maps.fleetengine.delivery.v1.DeliveryService.BatchCreateTasks | 180 |
帳單要求 | maps.fleetengine.v1.TripService.ReportBillableTrip | 9000 |
建立要求 | maps.fleetengine.delivery.v1.DeliveryService.CreateDeliveryVehicle, maps.fleetengine.delivery.v1.DeliveryService.CreateTask, maps.fleetengine.v1.VehicleService.CreateVehicle, maps.fleetengine.v1.TripService.CreateTrip |
3000 |
配送清單要求 | maps.fleetengine.delivery.v1.DeliveryService.ListTasks, maps.fleetengine.delivery.v1.DeliveryService.ListDeliveryVehicles |
3000 |
列出要求 | maps.fleetengine.v1.VehicleService.ListVehicles | 3000 |
讀取要求 | maps.fleetengine.delivery.v1.DeliveryService.GetDeliveryVehicle, maps.fleetengine.delivery.v1.DeliveryService.GetTask, maps.fleetengine.v1.VehicleService.GetVehicle, maps.fleetengine.v1.TripService.GetTrip |
9000 |
搜尋要求 | maps.fleetengine.delivery.v1.DeliveryService.GetTaskTrackingInfo, maps.fleetengine.v1.VehicleService.SearchVehicles, maps.fleetengine.v1.TripService.SearchTrips |
6000 |
更新要求 | maps.fleetengine.delivery.v1.DeliveryService.UpdateDeliveryVehicle, maps.fleetengine.delivery.v1.DeliveryService.UpdateTask, maps.fleetengine.v1.VehicleService.UpdateVehicle, maps.fleetengine.v1.VehicleService.UpdateVehicleAttributes, maps.fleetengine.v1.TripService.UpdateTrip |
30000 |
刪除要求 | maps.fleetengine.delivery.v1.DeliveryService.DeleteDeliveryVehicle, maps.fleetengine.delivery.v1.DeliveryService.DeleteTask, maps.fleetengine.v1.VehicleService.DeleteVehicle, maps.fleetengine.v1.TripService.DeleteTrip |
300 |
固定頻率限制
部分 API 方法會對單一資源執行作業,因此適用固定頻率限制。例如:providers/project_id/vehicles/vehicle_id
。Google 會對單一資源套用固定速率限制,所有客戶皆不例外。舉例來說,如果您在專案中,針對同一個 vehicle_id
每秒呼叫 maps.fleetengine.v1.VehicleService.UpdateVehicle
超過 3 次,預期會收到 HTTP 429
或 gRPC RESOURCE_EXHAUSTED
錯誤。
在 Google Cloud 控制台中,受影響的速率限制要求不會計為配額錯誤。
進一步瞭解如何處理錯誤。
配額類別 | 包含的 API | 每秒要求數 |
---|---|---|
單一資源讀取要求 | maps.fleetengine.delivery.v1.DeliveryService.GetTask,
maps.fleetengine.delivery.v1.DeliveryService.GetDeliveryVehicle, maps.fleetengine.delivery.v1.DeliveryService.GetTaskTrackingInfo, maps.fleetengine.v1.VehicleService.GetVehicle, maps.fleetengine.v1.TripService.GetTrip |
50 |
單一資源寫入要求 | maps.fleetengine.delivery.v1.DeliveryService.CreateTask,
maps.fleetengine.delivery.v1.DeliveryService.UpdateTask, maps.fleetengine.delivery.v1.DeliveryService.CreateDeliveryVehicle, maps.fleetengine.delivery.v1.DeliveryService.UpdateDeliveryVehicle, maps.fleetengine.v1.TripService.CreateTrip, maps.fleetengine.v1.TripService.UpdateTrip, maps.fleetengine.v1.TripService.ReportBillableTrip, maps.fleetengine.v1.VehicleService.CreateVehicle, maps.fleetengine.v1.VehicleService.UpdateVehicle, maps.fleetengine.v1.VehicleService.UpdateVehicleAttributes, maps.fleetengine.v1.VehicleService.ComputeTrafficData |
3 |