Canister Output Message Queue Limits, and IC Management Canister Throttling Limits

paulyoung · October 19, 2022, 4:34am

For #1, a quick search revealed this:

dfinity/ic/blob/a52bb83dd6fc99072db070ccc905478f5ce4bee4/rs/replicated_state/src/canister_state/queues.rs#L30-L30


      
          pub const DEFAULT_QUEUE_CAPACITY: usize = 500;

I also spotted this, which seems like it could further limit the number of messages:

github.com

dfinity/ic/blob/a52bb83dd6fc99072db070ccc905478f5ce4bee4/rs/replicated_state/src/canister_state/queues.rs#L1325-L1330


      
          /// Returns the memory required to push `req` onto an input or output queue.
          /// This is the maximum of `MAX_RESPONSE_COUNT_BYTES` (to be reserved for a
          /// response) and `req.count_bytes()` (if larger).
          pub fn memory_required_to_push_request(req: &Request) -> usize {
              req.count_bytes().max(MAX_RESPONSE_COUNT_BYTES)
          }

Topic		Replies	Views
[Discussion] Approaches for preventing canisters from hitting memory limits Developers Discussing	5	554	October 5, 2022
Can some one do a YouTube video on optimizing cross canister calls? Developers	3	518	February 2, 2023
Canister:limit for single message execution Developers	6	819	July 4, 2022
Scalable Messaging Model Roadmap community-consideration	63	1520	February 13, 2024
More info about "Locally timing out canister requests (Core Protocol)" Developers	9	317	April 24, 2023

Canister Output Message Queue Limits, and IC Management Canister Throttling Limits

Related Topics