Re: [Boost-users] [Serialization] std::set<std::string> restore performance
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 :
I wrote about that here http://webEbenezer.net/comparison.html. Ticket 2945 is related. https://svn.boost.org/trac/boost/ticket/2945 -- Brian Wood http://webEbenezer.net (651) 251-9384 "The kingdom of heaven is like a treasure hidden in the field, which a man found and hid again; and from joy over it he goes and sells all that he has and buys that field."
Thanks Robert and Brian. We'll revisit migration to 1.41. Last time we tried 3/4 months back, got some static assertion (if I remember correctly) related to some unsigned and signed comparison coming from archive code. And that time since it's not a must and we didn't have much bandwidth, we left it out. So, just a quick question - was that static assertion due to improper usage of the library or it's some bug in serialization library? If it's due to wrong usage, can you point me to related section of the doc? Regards, ~ Soumen -- View this message in context: http://old.nabble.com/-Serialization--std%3A%3Aset%3Cstd%3A%3Astring%3E-rest... Sent from the Boost - Users mailing list archive at Nabble.com.
Soumen wrote:
Thanks Robert and Brian. We'll revisit migration to 1.41.
Last time we tried 3/4 months back, got some static assertion (if I remember correctly) related to some unsigned and signed comparison coming from archive code. And that time since it's not a must and we didn't have much bandwidth, we left it out. So, just a quick question - was that static assertion due to improper usage of the library or it's some bug in serialization library? If it's due to wrong usage, can you point me to related section of the doc?
any static assertion or warnings are accompanied by notes in the source code where the assertion has been placed. These notes should point to the reasoning behind the assertion. Note that these notes might be a couple of stack frames back from the point where the message was issued. Robert Ramey
Regards, ~ Soumen
participants (3)
-
Brian Wood -
Robert Ramey -
Soumen