- play_arrow Understanding Junos OS
- play_arrow Junos OS Software Overview
- About the Overview for Junos OS
- Junos OS Overview
- Junos OS Architecture Overview
- Router Hardware Components
- Junos OS Routing Engine Components and Processes
- Junos OS Routing Processes
- Default Directories for Junos OS File Storage on the Network Device
- Junos OS Support for IPv4, IPv6, and MPLS Routing Protocols
- Junos OS Routing and Forwarding Tables
- Routing Policy Overview
- Junos OS Support for VPNs
- Configuring FIB Localization
- play_arrow Junos OS Security Overview
- play_arrow Junos OS Configuration Overview
-
- play_arrow Configuration Statements and Operational Commands
How to Improve Commit Time When Using Configuration Groups
You use configuration groups to apply configurations across other hierarchies without re-entering configuration data. You can specify every configuration detail in a configuration groups. You can also use wildcards in configuration groups to configure ranges of data, without detailing each configuration line. Another way to use configuration groups is to create an inheritance path that includes a long string of configurations to be applied.
When a configuration that uses configuration groups is committed, the commit process expands and reads all the configuration data of the group into memory to apply the configurations as intended. The commit performance can be negatively affected if many configuration groups are being applied, especially if the configuration groups use wildcards extensively.
If your system uses many configuration groups that use wildcards,
you can configure the persist-groups-inheritance statement
at the [edit system commit] hierarchy level to improve
commit time performance.
Using this option enables the system to build the inheritance path for each configuration group inside the database rather than in the process memory. This change can improve commit time performance. However, it can also increase the database size.
