|Anonymous | Login||2020-12-05 15:38 MSK|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0031920||Open CASCADE||[OCCT] OCCT:Application Framework||public||2020-11-11 17:33||2020-11-11 17:59|
|Target Version||[OCCT] 7.6.0*||Fixed in Version|
|Summary||0031920: Application Framework - speed up methods of getting label by entry and vise versa|
|Description||It's proposed to implement some cache for Label, Entry methods of TDF_Tool.|
When these methods are called for the same values, it takes too much time in a custom application. If we have some cache, it lets save time. If cache used, it requires additional memory for it. By this reason, it would be nice to make such cache optional. Then, the application might decide which way is more preferable.
It's proposed to implement it on OCCT side, not in the custom application because there are some internal places in OCCT, where this methods are also used, e.g.
STEPCAFControl_Reader for TDF_Tool::Entry,
XCAFPrs_DocumentExplorer, for TDF_Tool::Label.
The proposal of container is:
- tbb::concurrent_unordered_map<TCollection_AsciiString, TDF_Label, TCollection_AsciiStringHash, TCollection_AsciiStringEqual> m_ELCache;
(if tbb is used)
- std::map<TCollection_AsciiString, TDF_Label> m_ELCache;
|Tags||No tags attached.|
|Test case number|
|2020-11-11 17:33||nds||New Issue|
|2020-11-11 17:33||nds||Assigned To||=> mpv|
|Copyright © 2000 - 2020 MantisBT Team|