Optimization




Functionality After Before Result of changes
Server clusters.
Optimized operations with session data. The lags experienced by end users during the periods of high load on the session data storage in client/server mode are eliminated. Operations with session data required optimization. End users experienced lags during the periods of high load on the session data storage in client/server mode. Improved 1C:Enterprise usability.
Interface.
The impact on the total number of opened forms to the opening of new forms is reduced. The impact on the total number of opened forms to the opening of new forms was significant. Streamlined form opening when many other forms are open.
Queries.
In the query language, <EXPRESSION> OR TRUE expressions are optimized.

This change is not implemented in 8.3.7 compatibility mode.

The query language did not feature additional optimization of query texts. In some scenarios, the optimization increases the performance of dynamic lists and access restriction queries because the DMBS generates a simpler query plan.
Development tools.
The dump configuration to files and restore configuration from files operations are optimized for scenarios where the configuration includes a large number of managed forms. The performance of dump configuration to files and restore configuration from files operations was insufficient. In scenarios where the configuration is stored in an external system, improved performance of data exchange between the infobase and that system.
Database operations.
File infobase operations are optimized in the scenario where all of the following conditions are met:
  • A single client application accesses the infobase (Designer counts as a client application, too).
  • The client application and the database are located on different computers.
  • Both computers support SMB 2.1 protocol (operating system Windows 7 or later).
  • A significant number of database write transactions are performed.
In the specified scenario, the file infobase performance was insufficient. Improved performance of database configuration updates for file infobases in the scenario where Designer and the database are located on different computers.
Data exchange.
The performance of initial infobase image creation is improved.

The performance or reading records from independent nonperiodic information registers during the initial image creation is improved.

The performance of initial infobase image creation was insufficient. Faster creation of subordinate node infobases in distributed infobases.
DBMS operations.
Deletion of temporary table records during some PostgreSQL and IBM DB2 operations is optimized. The performance of temporary table record deletion during some PostgreSQL and IBM DB2 operations was insufficient. Improved performance of temporary table operations.
DBMS operations.
In client/server mode with Oracle Database DBMS, requests containing … IN (&ValueList) have a different execution algorithm when applied to lists containing more than 100 records.

This change is not implemented in 8.3.7 compatibility mode.

In client/server mode with Oracle Database DBMS, requests containing … IN (&ValueList) had a different execution algorithm when applied to lists containing more than 1000 records. Improved performance for some scenarios that include access to Oracle Database DBMS.
Administration tools.
Technological log.
Server clusters.
DBMS operations.
Getting DBMS lock data is optimized. The time required for getting the data does not depend on the number of infobases in the cluster.

The server cluster service that collects DBMS lock data is implemented. It is named AuxiliaryService (Utility cluster service).

The option to manage the collection of DBMS lock data is implemented in the technological log (<DBMSLOCKS> element). Enabling the data collection increases the DBMS load.

The time required for getting DBMS lock data depended on the number of infobases in the cluster.

The option to manage the collection of DBMS lock data using the technological log was not available.

Extended database diagnostics.
Administration tools.
Database operations.
In the file mode, infobase operations are optimized. To support the optimization, the file database data storage format is updated to new version 8.3.8 format. The option to change the page size of the infobase file (1Cv8.1CD) is implemented. The page size can have one of the following values: 4096, 8192, 16384, 32768, or 65536 bytes.

1C:Enterprise version 8.3.8 can open infobases created in the earlier 1C:Enteprise versions (and having version 8.2.14 database format) without changing their compatibility modes.

By default, new infobases have version 8.2.14 format. For the conf.cfg file, the DBFormatVersion parameter is implemented. It defines the format of newly created file-mode infobases.

For the infobase connection string, the DBFormat and DBPageSize parameters are implemented. They define the format and page size for new infobases.

To migrate data between infobase formats, you can use a .dt file (provided that the target infobase has the required format) or convert the infobase file using cnvdbfl utility. The cnvdbfl utility can change the infobase file page size during the conversion.

All infobases had the same format (version 8.2.14). Pages of the infobase file had fixed size: 4096 bytes. The option to change the size was not available. Reduced infobase opening time for infobases with large page sizes, and reduced query execution time.
Server clusters.
Reduced size of session data on the hard disk. Session data is stored in the server cluster in compressed form. Session data was stored in the server cluster in uncompressed form. The space occupied by internal cluster data is reduced. Some of the internal cluster operations are streamlined.
Client application.
Faster thin client startup in the file mode. The performance of the thin client startup in the file mode was insufficient. Faster thin client startup in the file mode.
Database operations.
Restructuring of separated hierarchical catalogs is optimized. The performance of restructuring separated hierarchical catalogs was insufficient. The performance of restructuring separated hierarchical catalogs is improved.
Database operations.
The RAM usage is reduced for restructuring a database that contains large amounts of binary data in file mode. Restructuring a database that contained large amounts of binary data in file mode might result in an unexpected shutdown due to insufficient RAM. Improved system stability for database restructuring in file mode.

Comments
0
Add comment