![]() On top of that, the page breaks themselves are actually single-row attributes it made little sense to store them in a container that was range-based. Because of this, storing that together with the hidden and filtered attributes unnecessarily increased the partition count, which in turn would slow down the query speed of all three attributes.Įven more problematic was the automatic page break attributes because the automatic page breaks always need to be set for the entire sheet, increasing the row limit significantly raised the partition count. First, the attributes stored together in this container had different distribution patterns, which caused over-partitioning of the container and unnecessarily slowed down the queries of all stored attributes.įor instance, the hidden and filtered attributes are distributed in a very similar manner, but the manual height attribute is not necessarily distributed in a manner similar to these attributes. ![]() There were primarily two problems with this storage scheme that made the container non-scalable. Searching for the value of an attribute for an arbitrary row was performed linearly from the first record since the core of the container itself was simply just an array. They were stored per range, not per individual row or column, so that if a range of rows had identical set of attribute values over the entire range, that attribute set would be stored as a single record.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |