You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/nrf/protocols/matter/getting_started/memory_optimization.rst
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -415,7 +415,14 @@ The static size is determined by the :kconfig:option:`CONFIG_CHIP_MALLOC_SYS_HEA
415
415
To use a dynamic heap size on your Matter device, set them both to ``n``.
416
416
417
417
The static heap size means that you can define the maximum heap size for your application by setting the :kconfig:option:`CONFIG_CHIP_MALLOC_SYS_HEAP_SIZE` Kconfig value.
418
-
You can also adjust the heap dedicated for MbedTLS purposes by setting the :kconfig:option:`CONFIG_MBEDTLS_HEAP_SIZE` Kconfig option value.
418
+
You can also adjust the heap dedicated for Mbed TLS purposes by setting the :kconfig:option:`CONFIG_MBEDTLS_HEAP_SIZE` Kconfig option value.
419
+
420
+
Packet buffer pool size
421
+
-----------------------
422
+
423
+
The Matter application uses a fixed-size pool for packet buffer memory management.
424
+
The pool size is determined by the :kconfig:option:`CONFIG_CHIP_SYSTEM_PACKETBUFFER_POOL_SIZE` Kconfig option.
425
+
You can adjust the pool size to reduce the memory usage of your application, but that can have a negative effect on the performance of the application.
419
426
420
427
.. note::
421
428
The Thread protocol has a separate configuration for memory allocation.
0 commit comments