Re: [Boost-users] [Multi-Index] performance difference between lower_bound() and upper_bound()

Subject: Re: [Boost-users] [Multi-Index] performance difference between lower_bound() and upper_bound()
From: Joaquín Mª López Muñoz (joaquin_at_[hidden])
Date: 2013-11-29 04:34:45

El 28/11/2013 13:55, Dominique Devienne escribió:

By not taking the full-range into account, I was not really getting the "max suffix", so when I was trying to insert a new entry with name "$prefix $max_suffix_int", I was again getting a conflict, which triggered another loop necessary for a different conflict resolution scheme (the new one is supposed to find a non-conflicting name in a single pass, at the cost of scanning the range of possible conflicts to find the max_suffix_int of really conflicting entries - some entries have the same name, butother keys make them non-conflicting).

I also tested that both lower_bound(prefix + " :") and upper_bound(prefix + " 9999999999") (I use an int32_t suffix) give me the same upper range iterator, with similar performance.

Watch out: depending on how your strings look like, these two bounds are not equivalent. For instance:

  "p 9999999999" < "p 9999999999 foo" < "p :"

I understand you're already taking this into account, but wanted to point it out just in case. Best,

Joaquín M López Muñoz
Telefónica Digital

________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx