|
For each type of distribution, the available data memory present in the applied controller may limit the amount of kernel objects that can be created, regardless the figures specified in above table. The figures presented for the Basic and Standard distribution are maximum values given enough data memory is present. In case data memory gets exhausted before reaching the specified figure no more kernel objects can be created notwithstanding the figure specified above. For the Extended distribution, the amount of data memory is the only limiting factor.
To successfully run AVIX-16, the practical minimum amount of RAM a controller should have is 2KB.
To successfully run AVIX-32, the practical minimum amount of RAM a controller should have is 4KB.
When using AVIX-16 with a 33FJ256GP710 controller with a maximum of 31 priorities, a system stack of 300 bytes, a message body size of 8 bytes and using no heap, the following maximum values apply: ~135 threads with a 150 byte stack, or ~1650 event groups or ~1650 semaphores or ~1480 mutexes or ~930 timers or ~570 pipes with a 10 byte buffer or ~190 memory pools with 10 memory blocks of 10 bytes each.
When using AVIX-32 with a 32MX360F512L controller with a maximum of 31 priorities, a system stack of 800 bytes, a message body size of 8 bytes and using no heap, the following maximum values apply: ~113 threads with a 150 byte stack, or ~950 event groups or ~950 semaphores or ~840 mutexes or ~580 timers or ~380 pipes with a 10 byte buffer or ~135 memory pools with 10 memory blocks of 10 bytes each.
No rights can be derived from these figures.
These figures are based on AVIX version 3.5 and are meant to give an impression of its capabilities.
These figures may change with future versions of AVIX.
|
