Main > Knowledge Base > Knowledge Base > Knowledge base > Practical developer guide 8.3 > Lesson 14 (3:20). Optimization of posting the Services document > Theory. Understanding cache > Practical developer guide 8.3 > Lesson 14 (3:20). Optimization of posting the Services document > Theory. Understanding cache

Theory. Understanding cache

In section Theory. Referential data usage specifics we have mentioned that the platform has a cache that stores object data read from the database. Now we will discuss this feature in more detail.

1C:Enterprise caches database objects that are read from the database using object operations.

When you access object attributes using a reference, the platform accesses the object cache that is stored in RAM.

The object cache consists of two parts: the transactional cache and the standard cache. Which cache is used depends on whether the reference is made in the context of a transaction or not (fig. 14.33).


Fig. 14.33. Object cache

All the data stored in the cache is intended to be read-only. This means that all the data that is read by reference is handled using the object cache, while writing is handled using 1C:Enterprise object operations.

Next page: Standard cache




© 1C LLC. All rights reserved
1C Company respects the privacy of our customers and visitors
to our Web-site.