replace or aqString.Replace ? Beware of speed
Needed to work on address normalization so used aqString.Replace ..
Works fine but tooooo slow ..
Done a little test and found that aqString.Replace is awfully slow ... really ..
...
Forum Discussion
100 iterations of aqString.Replace => 6 seconds
😮 It is slow!
In fact, 100 itérations of the method which has 22 aqString.replace -> 2200 aqString.Replace in 6 seconds.
Seem nice but if you compare with native replace it is slow.
If no need of big amount of replacement, aqString.Replace is enough and convenient.
If need of speed and large scale of data, it's not enough.
On my project, needed to work on more than 1M replacements ... and target time is under the hour ...The optimized replace version was the solution.
