# Critical Bus load

**URL:** <https://forum.opencyphal.org/t/critical-bus-load/493>\
**Category:** Applications & Usage\
**Created:** [May 27, 2019, 3:32pm UTC](https://forum.opencyphal.org/t/critical-bus-load/493 "2019-05-27T15:32:44Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pavel.kirienko](https://forum.opencyphal.org/user_avatar/forum.opencyphal.org/pavel.kirienko/32/9_2.png) [@pavel.kirienko](https://forum.opencyphal.org/u/pavel.kirienko)\
**Post date:** [May 31, 2019, 8:28am UTC](https://forum.opencyphal.org/t/critical-bus-load/493/4 "2019-05-31T08:28:37Z")

</div>

There is no one-size-fits-all bus utilization limit. You should analyze your bus from the standpoint of latency constraints per every type of message exchanged over it; this question is briefly explored in the section 4.1.4 “Transfer priority” of the Specification: [https://new.uavcan.org/specification/UAVCAN\_Specification\_v1.0.pdf;](https://new.uavcan.org/specification/UAVCAN_Specification_v1.0.pdf;) also, this thread may also be of relevance: [Transfer priority level mnemonics](https://forum.opencyphal.org/t/transfer-priority-level-mnemonics/218)

---

_[View the full topic](https://forum.opencyphal.org/t/critical-bus-load/493)._