|Functionality||After||Before||Result of changes|
||The full-text search algorithm is optimized for scenarios where a search string is used multiple times (for example, getting the next batch of search results).
The full-text search algorithm is optimized for scenarios where a user does not have access rights for some objects returned by the search.
|The full-text search performance was insufficient.||Improved full-text search performance for infobases containing a large number of items, and also in scenarios where a user does not have access rights for some objects returned by the search.|
||Optimized memory usage for fuzzy search (the search that uses the # operator). The search for similar words is optimized.||Fuzzy search might cause a memory overflow which, in turn, caused the system shutdown.
The search for similar words might take a long time.
|Increased stability of the fuzzy search in scenarios where the full text search index has a large size.|
||The web client performance is improved in the following scenarios:
The web client now uses Google Closure Compiler.
|The web client performance was insufficient.||Improved web client performance.|
||The loading time of 1C:Enterprise script modules is slightly reduced.||The loading of 1C:Enterprise script modules was not fast enough.||Slightly reduced startup time for applied solutions that include a large number of 1C:Enterprise script modules.|
||The startup time of the client application (before the authentication dialog appears) is slightly reduced.||The client application startup was not fast enough.||Slightly reduced startup time of the client application.|
||The performance of the following operations is improved:
The performance of compatibility mode change operations is improved.
The 1C:Enterprise version 8.3.3 compatibility mode is implemented for configuration repositories.
The configuration repository performance is improved in scenarios where the configuration repository compatibility mode is set to Do no use.
|The performance of configuration repository operations was insufficient.||Improved configuration repository performance.|
||The strong data compression algorithm for large data volumes (more than 64 KB) transferred between the client and the server (or a web server extension) is optimized. This slightly reduces the time required to open managed forms in the thin client connected to a web server (both in the file and client/server modes), and also in the scenario with a direct connection in the client/server mode.||The strong data compression algorithm was less efficient.||Slightly reduced time of opening managed forms in the thin client connected to a web server (both in the file and client/server modes), and also in the scenario with a direct connection in the client/server mode.|
|Web services and HTTP services.
||Faster processing of requests that call the standard OData interface.||Performance of requests that called the standard OData interface was insufficient.||The performance of operations with the standard OData interface is improved.|
||Improved performance of opening managed forms in the following scenarios:
||The performance of opening managed forms in the listed scenarios was lower.||Improved usability of managed forms.|
||Managed form conditional appearance is optimized.||The performance of managed form conditional appearance was lower.||Improved usability of managed forms with conditional appearance.|
||Performance of base configuration updates (update configuration from file, load configuration from file, and get specific configuration version from configuration repository) is improved.||Performance of base configuration updates was insufficient.||Better usability for developers.|
|For the file mode, the option to restructure the infobase so that all data required to open the infobase is at the beginning of the 1Cv8.1CD file is implemented. This improves the performance of infobase opening.
This type of restructuring is performed during the compressing of infobase tables (which is available from a Designer dialog box and as a command-line option), or during infobase verification with the chdfl utility with the Correct errors check box selected.
It is recommended that you always perform this optimization after you make any configuration changes (and the associated infobase restructuring) that result in database structure changes.
|Internal information required for opening an infobase was evenly distibuted within the 1Cv8.1CD infobase file.||Improved performance of opening file infobases, especially in scenarios where the infobase is located on a network resource.|
||In client/server mode with PostgreSQL DMBS, the query that is executed when deleting records from tables of extra dimensions of accounting registers is optimized.||In client/server mode with PostgreSQL DMBS, the performance of the query that was executed when deleting records from tables of extra dimensions of accounting registers was insufficient.||Improved performance of deleting accounting register records.|