|Functionality||After||Before||Result of changes|
|Operating with DBMS. Accumulation registers. Working with queries.||Optimized performance of accumulation register virtual tables when obtaining totals with a filter that does not include all dimensions.||Insufficient performance of accumulation register virtual tables when obtaining totals with a filter that did not include all dimensions.||Performance of accumulation register virtual tables is increased.|
|Server cluster.||Creation of new sessions is optimized.||Creating of new sessions was performed inefficiently.||Optimized performance when establishing connections to the 1C:Enterprise server in the following cases:|
|Information registers.||Improved performance of independent, non-periodic information registers that have more than 1 dimension. This change is not implemented in 8.3.2 compatibility mode.||Insufficient register performance.||Increased speed of writing to a register, especially when a large number of users are working.|
|Applied objects.||Optimized selections from catalogs and charts of characteristic types for certain scenarios.||In certain scenarios performance of selections from catalogs and charts of characteristic types was inefficient.||Increased performance of selections from catalogs and charts of characteristic types in certain scenarios.|
|Dynamic list.||Improved dynamic list performance in client/server mode when a large number of users are working.||In certain scenarios dynamic list performance was insufficient.||Improved dynamic list performance in certain scenarios.|
|Server cluster.||Optimized processing of session data for some scenarios.||In some scenarios processing of session data was inefficient.|
Improved performance and scalability of 1C:Enterprise servers.
|Accumulation registers.||Optimized execution of queries to turnovers registers with a large number of dimensions that include aggregates (for some scenarios). This change is not implemented in 8.3.2 compatibility mode.||In some cases execution of queries to turnovers registers with a large number of dimensions that included aggregates was inefficient.||You can use aggregate functions in more scenarios than before.|
|Operating with DBMS.||In order to optimize some queries to IBM DB2 DMBS, the recommendation to run the db2set DB2_OVERRIDE_BPF=5000 command and then restart the DBMS is included into the documentation. Methods of detecting situations when the optimization is required are also described in the documentation.||Some queries to IBM DB2 DBMS were performed inefficiently.||Optimized performance during the execution of some types of IBM DB2 DBMS queries.|
|Information registers.||For periodic information registers that are subordinate to recorders, the Active field is listed in the following indexes:|
The Active field is the last one in these indexes. After changing the compatibility mode, full infobase restructuring must be performed for rebuilding indexes. This change is not implemented in 8.3.2 compatibility mode.
|The Active field was not included in the list of indexes of periodic information registers subordinate to recorders.||Improved performance when retrieving the first and the last slices.|
|Server cluster.||1C:Enterprise server is optimized to reduce memory usage and fragmentation.||In some scenarios, 1C:Enterprise server used memory inefficiently. This led to memory fragmentation and increased memory consumption.||Reduced memory consumption of 1C:Enterprise server, and lower memory fragmentation. This allows to reduce the number of planned 1C:Enterprise server restarts and improves the system stability.|
|Operating with DBMS.||Indexes of attributes with additional ordering include deletion marks and all fields that are indexed with additional ordering. This data is added to the end of the index.||Indexes of attributes with additional ordering did not include deletion marks and all fields that were indexed with additional ordering.|
Improved performance of dynamic lists filtered by multiple attributes (including the deletion mark).
|Managed form.||Optimized performance of displaying managed forms after server calls (both explicit and implicit ones) that change the form appearance.||Forms were not displayed fast enough when their appearance was changed from 1C:Enterprise script.||Optimized performance of displaying forms, for example, when the displayed title of a form element is modified.|
|Common attributes / Data separation.||Once the version 8.3.2 compatibility mode is disabled, optimization is performed on the structure that stores data on the table separators connected to objects included in the separator contents. When the version 8.3.2 compatibility mode is enabled, the reverse restructuring of the database tables is performed.||The structure that stored separator data was not optimal.||Improved performance due to the changes in the structure that stores separator data.|
|Server cluster.||In server cluster, the algorithm for balancing the working process load is optimized. The following parameters are used in addition to parameters used in the previous versions to define the available server performance: size of CPU queue, current processor load, and number of CPU cores. Values used for defining the available server performance are recorded to the TXT property of the CLSTR event in the technological log. To obtain performance parameters, the user on whose behalf the 1C:Enterprise server is running must be included in the Performance Log Users group.||In the server cluster, the algorithm for balancing the working process load took less number of parameters into account.||Improved reactivity of the load balancing algorithm. The algorithm defines overloaded CPUs and stops sending new tasks to them.|
|Managed form.||Optimized performance of opening managed forms with multiline text boxes that contain a large number of line breaks.||Performance of opening forms with multiline text boxes containing a large number of line breaks was not high enough.||Forms with multiline text boxes that contain a large number of line breaks are opened faster.|