You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and run mvn test before and after your change. It will measure in a rough but sufficiently accurate manner the running time of the string estimation.
We want to make sure that we do not degrade the performance since this function is called repeatedly, possibly millions of times. It also does something that is relatively unimportant (produce a memory usage estimation) so we do not ever want it to have an impact on performance.
Activity
lemire commentedon Oct 6, 2016
@j-joker
This seems to be a valid issue. I think we should round-up to the word size (64 bits on a 64-bit machine and 32 bits on a 32-bit machine).
Care to issue a PR? This way you'd get credit for the (small) change.
lemire commentedon Oct 6, 2016
(I am repeating this comment from the PR to make sure it does not get lost:)
Please merge the following commit
a5886f7
and run
mvn testbefore and after your change. It will measure in a rough but sufficiently accurate manner the running time of the string estimation.We want to make sure that we do not degrade the performance since this function is called repeatedly, possibly millions of times. It also does something that is relatively unimportant (produce a memory usage estimation) so we do not ever want it to have an impact on performance.
Here is what it might look like...
lemire commentedon Oct 31, 2017
This remains unresolved, we may underestimate the memory usage. Some analysis is needed.