7 Apr
2010
7 Apr
'10
4:27 p.m.
Soumen wrote:
Recently we're profiling our tool for restoration for a large electronic design. And we're restoring two archive of same number of elements - one uses vector as container while the other uses set. And it appears that restoration of set is much much slower than the vector. Both the restoration called from same parent which is called just once. And vector restoration took 2% of parent while set restoration took 83% of parent. And most of set restoration time is spent in :
Changes since 1.35 in the loading of set<...> should make it measurable faster to load sets than the 1.35 version. Robert Ramey