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
It might be worth using RegexOptions.ECMAScript in C# benchmark, or just add another bench for c# with this option. It drops some 'advanced' features like Unicode support, which increases performance in ~1.5-2 times.
I understand that it's a questionable decision, and I could mention some pros and cons here:
We are competing with different regex engines, and some of them, like JS one, as far as I'm aware, does not support UTF. So it's a bit unfair to compare motorbike with a truck.
It looks like we compare default regex usage patterns, and I have never seen anyone use RegexOptions.ECMAScript in a real life.
My results (Windows 10, dotnet core 2.1.4):
Original
1824.7035 - 92
1560.8753 - 5301
109.0058 - 5
With ECMAScript
1072.2842 - 92
908.0764 - 5301
110.9607 - 5
The text was updated successfully, but these errors were encountered:
It might be worth using
RegexOptions.ECMAScript
in C# benchmark, or just add another bench for c# with this option. It drops some 'advanced' features like Unicode support, which increases performance in ~1.5-2 times.I understand that it's a questionable decision, and I could mention some pros and cons here:
RegexOptions.ECMAScript
in a real life.My results (Windows 10, dotnet core 2.1.4):
Original
With ECMAScript
The text was updated successfully, but these errors were encountered: