tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
TDMQ for Apache Pulsar
    Documentation
    Download PDF

    Virtual Cluster Billing

    Last updated: 2024-08-14 10:51:20
    Download PDF
      This document describes the pricing details and free tiers of each billable item of TDMQ for Apache Pulsar virtual cluster.

      Pay-as-You-Go

      API call price

      TDMQ for Apache Pulsar virtual cluster adopts tiered pricing for API calls. API call fees = (number of API calls for message sending + number of API calls for message consumption) * API call unit price.
      The unit price of API call (USD/million calls) is as shown below:
      Billing Tier
      API Calls (Million/Month)
      Call Unit Price (USD/Million Calls)
      Guangzhou, Shanghai, Nanjing, Beijing, Chengdu
      Hong Kong (China), Singapore, Seoul, Silicon Valley, Frankfurt
      Shenzhen Finance, Beijing Finance
      Tier 1
      N ≤ 1,000
      0.3265
      0.2512
      0.4019
      Tier 2
      1,000 < N ≤ 5,000
      0.2939
      0.226
      0.3617
      Tier 3
      5,000 < N ≤ 10,000
      0.2449
      0.1884
      0.3014
      Tier 4
      10,000 < N ≤ 50,000
      0.2122
      0.1633
      0.2612
      Tier 5
      N > 50,000
      0.1959
      0.1507
      0.2411
      The maximum message body size is 5 MB, and the number of API calls is calculated at different rates according to the message size:
      Message Size
      Rate
      N ≤ 2 KB
      1
      2 KB < N ≤ 4 KB
      2
      4 KB < N ≤ 16 KB
      4
      16 KB < N ≤ 100 KB
      16
      100 KB < N ≤ 1 MB
      64
      1 MB < N ≤ 5 MB
      256
      For example, one 10 KB message (publishing or subscribing) request will be charged as 4 API calls.
      Note:
      The number of API calls for consuming messages refers to the number of messages pushed by the broker to consumers, which may be numerically greater than the number of messages actually acknowledged by consumers. Scenarios where this happens include:
      1. When a large number of messages are retained, consumers will prefetch a certain number of messages during connection, and multiple unacknowledged messages will be recorded as multiple API calls for consuming messages. In this case, the number of API calls for consuming messages will be greater than the number of messages actually acknowledged by consumers.
      2. When tag messages are consumed, multiple consumers are usually started. In this case, the number of API calls for consuming messages will be greater than the number of messages actually acknowledged by consumers.

      Message storage price

      TDMQ for Apache Pulsar virtual cluster adopts linear billing for message storage. Message storage fees = message storage size * message storage unit price.
      Note:
      TDMQ for Apache Pulsar stores a message in three copies by default. Therefore, the billable storage capacity is three times of the total message size.
      The unit price of message storage (USD/GB/hour) is as shown below:
      Region
      Guangzhou, Shanghai, Nanjing, Beijing, Chengdu
      Hong Kong (China), Singapore, Seoul, Silicon Valley, Frankfurt
      Shenzhen Finance, Beijing Finance
      Unit price (USD/GB/hour)
      0.0003
      0.0003
      0.0006
      Note:
      1. When the message retention policy is set to persistent retention, even if a message is consumed, it will still be persistently stored according to the maximum retention time, resulting in additional message storage fees.
      2. In TDMQ for Apache Pulsar, message data is stored on the Bookie storage node of the BookKeeper cluster in the form of ledger. Even if deletion after consumption is configured, when the ledger is turned on, the async cleaner will not clear the message data. If some messages are not consumed for a long time, other messages in the same ledger may keep consuming the storage space, resulting in additional message storage fees.

      Partition topic resource usage price

      TDMQ for Apache Pulsar virtual cluster adopts linear billing for partition topic resource usage. Partition topic resource usage fees = number of partition topics * partition topic resource usage unit price.
      The number of partition topics in TDMQ for Apache Pulsar refers to the sum of all partitions of all topics; that is, if there are two three-partition topics, the number of partition topics is 2 * 3 = 6.
      The unit price of partition topic resource usage (USD/piece/day) is as shown below:
      Region
      Guangzhou, Shanghai, Nanjing, Beijing, Chengdu
      Hong Kong (China), Singapore, Seoul, Silicon Valley,and Frankfurt
      Shenzhen Finance, Beijing Finance
      Unit price (USD/piece/day)
      0.025
      0.032
      0.040
      Note:
      The partition topic resource usage fees in TDMQ for Apache Pulsar virtual cluster are charged by day; that is, a partition topic resource created at any time on a natural day will incur a full day's fees on the next natural day even if its actual usage time is less than 24 hours.

      Free Tiers

      TDMQ for Apache Pulsar offers certain free tiers to each root account for pay-as-you-go billable items in each region:
      Billable Item
      Free Tier
      Accumulation Method
      API call
      10 million
      Accumulated monthly by region
      Message storage
      1 GB
      Accumulated monthly by region
      Partition topic
      2000
      Accumulated monthly by region
      The free tiers will be used first to deduct the cumulative usage of all clusters in each region under each root account, and they are shared between different clusters in the same region.
      Contact Us

      Contact our sales team or business advisors to help your business.

      Contact Us
      Technical Support

      Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

      Submit a Ticket
      7x24 Phone Support
      Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
      Privacy PolicyLegalCookie Policy