Skip to main content

Asynchronous Regex Matching and Highlighting

I came across a question on StackOverflow the other day where someone was trying to find the culprit for an unusually slow running regular expression. In fact it'd take around 30 seconds to execute. This was a rather extreme case of catastrophic backtracking. With just a few minor tweaks someone was able to drastically improve the performance, making it about 48,000 times faster. Yeah, pretty drastic and it really illustrates the importance of running a simple benchmark to test any regular expression that'll see heavy use.

It's rare that someone will write such a poor performing regular expression, especially by accident. But nevertheless, this circumstance is one where Regex Hero failed miserably. The trouble is that the regular expression was evaluated synchronously as you type. So if you're dealing with a slow running regular expression, this would actually hang the UI temporarily until it's finished. It was an ugly thing. But no more. As of today, Regex Hero now evaluates the regular expression on a separate thread, returns the results, and then highlights the matches. This asynchronous approach is much more user friendly as the UI is always responsive. In addition to this, by running the regular expression on a separate thread from the UI, Regex Hero is able to take better advantage of multi-core processors, actually improving the overall performance of the application. These are all good things. I hope you enjoy it.


Popular posts from this blog

Regex Hero for Windows 10 is Underway

Awhile back I began working on an HTML5 / JavaScript version of Regex Hero . However, it was a huge undertaking essentially requiring a complete rewrite of the entire application. I have not had enough time to dedicate to this lately. So I've begun again, this time rewriting Regex Hero to work in WPF. It'll be usable in Windows 10 and downloadable from the Microsoft Store. This is a much easier task that also has the advantage of running the .NET regex library from the application itself. This will allow for the same speedy experience of testing your regular expressions and getting instant feedback that Regex Hero users have always enjoyed. I expect the first release to be ready in Q4 of 2019.

Installer for Desktop version of Regex Hero

As Firefox just dropped support for Silverlight I really needed a solution for Regex Hero. So I created an installer for it. It's still Silverlight, but by using the installer you can install it directly to your computer and never need to open it in a browser. If you visit and don't have a browser that supports Silverlight (IE is the only one left), then you'll see download links for 64-bit and 32-bit versions of the installer. When you install it you'll see a link over on the right hand side that says "Activate Regex Hero". This process connects your desktop version of Regex Hero with your online account. So if you're a licensed user this is how you'll gain access to all of those licensed features. Note: Currently there will be a security warning when you try to run either one of these installers. I'm in the process of obtaining a code signing certificate and will update them as soon as possible. You may be wondering a

Optimizing Your Regular Expressions

Regular expressions will backtrack.  That's an unfortunate thing about them because backtracking can be slow.    And in certain (rare) cases the performance can become so awful that executing the regular expression against a relatively short string could take over a minute.  There's a good article about catastrophic backtracking over at . And today I created a video about all of this called  Regex Lesson 5: Optimization .  In the video I start with a very poorly written regular expression and make several improvements to it, using the benchmarking feature along the way.  By the end of the video I make the regular expression over 3 million times faster. In addition, today's update to Regex Hero provides a little message in the event that you encounter a regular expression that takes over 10 seconds to evaluate... And then last of all, I changed the benchmarking feature a bit.  In the past it would simply test your regular expression against