For better code size performance, it's recommended to not to use a bigger counter/reload/compare register for timer than is necessary. Otherwise the code size generated by a component may be increased (for example, for 8-bit timer choose 8bit timer register).
In some cases, several timing periods are required when using timers (for example, the TimerInt component). The Processor Expert allows changing the timer period during run-time using several ways (note that this is an advanced option and the Component Inspector Items visibility must be set to at least 'ADVANCED').
These ways of changing the run-time period of timer requires various amount of code and thus the total application code size is influenced by the method chosen. When the period must be changed during run-time, use fixed values for period instead of an interval if possible to save code. There are two possibilities (See Dialog for timing settings for details):
If the application requires only a few different timing periods, even if the functionality is the same for both cases, the correct usage of list of periods produces smaller code compared to code using an interval.