Investigate speed regression after 2.1.0

[XhmikosR]

Initially noticed it on #954 (comment)

C:\Users\xmr\Desktop>curl https://upload.wikimedia.org/wikipedia/commons/archive/2/2e/20180507223736%21Germany_%28%2Bdistricts_%2Bmunicipalities%29_location_map_2013.svg>1.svg
C:\Users\xmr\Desktop>npm i svgo@2.1.0 -g
C:\Users\xmr\AppData\Roaming\npm\svgo -> C:\Users\xmr\AppData\Roaming\npm\node_modules\svgo\bin\svgo
+ svgo@2.1.0
added 1 package from 1 contributor and updated 1 package in 1.848s

C:\Users\xmr\Desktop>set NODE_OPTIONS=--max_old_space_size=8192 && svgo 1.svg -o 2.svg

1.svg:
Done in 164252 ms!
74491.22 KiB - 49.3% = 37749.765 KiB

C:\Users\xmr\Desktop>npm i svgo@latest -g
C:\Users\xmr\AppData\Roaming\npm\svgo -> C:\Users\xmr\AppData\Roaming\npm\node_modules\svgo\bin\svgo
+ svgo@2.2.2
removed 1 package and updated 1 package in 1.521s

C:\Users\xmr\Desktop>set NODE_OPTIONS=--max_old_space_size=8192 && svgo 1.svg -o 2.svg

1.svg:
Done in 355186 ms!
74491.22 KiB - 49.3% = 37737.378 KiB

---

https://github.com/svg/svgo/compare/v2.1.0...v2.2.2?w=1

So far I've noticed this:

• 04b2ae9?w=1 -> +~8-9% speed penalty
• 2f3c35d?w=1 -> +~10% speed penalty
• The precision patches seem to also add pretty big increase too (more than 10%):
  • e2ec7e8?w=1
  • d58a7e6?w=1

Results may vary on other machines/OS'es

[TrySound]

Solved in https://github.com/svg/svgo/releases/tag/v2.4.0