New records, giving an almost seamless experience to the user. Then when delta changes came in, the value getters were only executed on the Introducing the value cache meant the value getters were execute once when the initial data was loaded, so Stall for around 1,000ms as rows were added. Recomputed the aggregations, resulting in all the value getters getting called again, causing the grid to This meant, if more rows were added, the grid The client was also groupingĪnd the summing by the columns containing the value getters. Maths, using third-party maths API in the valueGetter for 8 of the columns. One client of AG Grid had 1,000 rows and 20 columns in a grid. This value cache is for advanced users who have time-consuming value getters and want to speed up their applications by introducing a cache to reduce the number of times value getters get executed. If the data in the grid has not changed since the last time the value getter was used, then the value is retrieved from the cache instead of executing the value getter again. When the value cache is turned on, each time a value getter is executed, its result is stored in the value cache. If this is the case, then you can opt to turn on the value cache to store the results of the value getters. However sometimes you might implement time-intensive tasks in your value getters. For most use cases, this will not be an issue, as value getters will execute quickly and not have any noticeable performance implications for your application. If you are not using value getters, then you do not need the value cache.Įach time the grid requires a value from a value getter, the value getter is executed. The value cache is used for the results of value getters.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |