office-gobmx/svl
Armin Le Grand (allotropia) fd2aaac247 ITEM: Add measurements for SfxItemSet usages (debug only)
I was wondering how much of that arrays of pointers
to SfxPoolItems is actually used in the SfxItemSets in
real office runtime, so I added code now to measure that.

It does use the state of the ItemSet at destruction,
so it is possible that items were added/removed which
are not covered, but most cases of internal usages do
not do that.

I then check/sort the collected data at office shutdown,
it will be printed as SAL_INFO when svl.items/vcl.items
is set, so use this to see the data.

This gives info about the average space utilization in
different ItemSets with different sizes, also gives an
insight about used ItemSet sizes and amount of their
usages.

Of course results differ from app to app and dependent
of what is done with the office, but interestingly when
using quite some files opening from all apps it
toggles/normalizes to something around 20-25%...

Change-Id: I3eb2f0401c39a5bdb5d1d8176e95df07be4c111a
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166455
Reviewed-by: Armin Le Grand <Armin.Le.Grand@me.com>
Tested-by: Jenkins
2024-04-23 09:39:47 +02:00
..
inc/pch
qa improve loplugin:staticmethods 2024-03-22 11:47:36 +01:00
source ITEM: Add measurements for SfxItemSet usages (debug only) 2024-04-23 09:39:47 +02:00
unx/source/svdde
util
AllLangMoTarget_svl.mk
CppunitTest_svl_adrparse.mk
CppunitTest_svl_inetcontenttype.mk
CppunitTest_svl_items.mk
CppunitTest_svl_lngmisc.mk
CppunitTest_svl_lockfiles.mk
CppunitTest_svl_notify.mk
CppunitTest_svl_qa_cppunit.mk
CppunitTest_svl_urihelper.mk
IwyuFilter_svl.yaml
JunitTest_svl_complex.mk
Library_fsstorage.mk
Library_passwordcontainer.mk
Library_svl.mk
Makefile
Module_svl.mk
README.md

Non-Graphical Helper Code (svtools light)

Contains non-graphical helper code for office applications.

Specifically this module does not depend on or use includes from module vcl. Originally all code in svtools that did not depend on vcl was split off into this svl ("svtools light") module.

In particular the SfxItemSet is a property-bag like container that stores arbitrary sets of properties for everything from text run formats, to Chart regression line properties.

There are lots of other useful helpers in here for various office tasks; much of this code was originally moved from svx/sfx2.

Items, Pools and Sets

SfxPoolItem

A small reference counted piece of data. Many subclasses, each with a unique integer to identify its type (WhichId). Can be compared for equality (operator==), Clone()d, and converted to/from uno::Any (QueryValue/PutValue).

A pool item may have value semantics ("poolable"), meaning that there will generally be only one instance that compares equal per item pool, or not, in which case the item will be Clone()d quite a bit.

SfxItemPool

Usually there is one item pool per document, with a range of valid WhichIds that is specific to the type of document.

The item pool owns all instances of SfxPoolItem or its subclasses that have ever been added to an item set. It also contains a default item for every WhichId, which will be (depending on parameters) returned from item sets if the set does not contain an item at this WhichId.

SfxItemSet

The item set can be created with a user-supplied range of WhichIds; it will accept SfxPoolItems with matching WhichIds and ignore attempts to insert items with non-matching WhichIds.

Items that are successfully inserted into the set will be stored in the set's SfxItemPool, and for poolable items only a single instance that compares equal under the predicate operator== will be stored in the pool, regardless of how many sets contain it, thus conserving memory.

There are members m_pWhichRanges for the valid ranges (as pairs of WhichIds), m_nCount for the number of items contained, and m_pItems for the pointers to the actual items.