Skip to main content

Improving Perceived Performance

Ah yes, perceived performance: it can be such an underrated thing. I thought Regex Hero was still loading a little slow for a ~50KB application.

In fact I looked at this a couple months ago and found that my initialization code was preventing the Regex Hero UI from appearing until it was done. As such, you'd actually be looking at a blank screen a little longer than you should.

When talking about perceived performance, a blank screen like this is just about the worst user experience possible because in the back of the user's mind they might be thinking, "Did this application just hang?" Even if they don't think that, any kind of prolonged stillness can be perceived as slowness and that's the last thing I want. So at the time I tried a few things to correct this but couldn't find a good solution that worked well and didn't cause any other problems.

Today I took another crack at it and finally solved the problem. You'll notice now that when it loads you'll briefly see the default Silverlight loading animation as you always have. And then where you'd normally see a blank screen, you'll instead see this loading box on top of the Regex Hero app for about half a second.

To be sure I actually made some progress with this I made some crude measurements. I measured the load time until you actually see the Regex Hero UI with the old method vs the time until you see the new loading box in the new method. After multiple tests and averaging the results here's what I came up with:

Before: 1.6 seconds
1.1 seconds

(Note that this test was done with a cached copy to take bandwidth variances out of the equation.)

All that work for half a second of improved "perceived" performance may seem like a waste of time. After all, the time it takes before you're able to actually use Regex Hero hasn't changed. It's still going to be around 2 or 3 seconds on the first load and about 1.6 seconds once it's cached (actual mileage may vary).

But in my mind, seeing a glimpse of the Regex Hero UI half a second sooner is huge. I think when you work with applications that load quickly and respond immediately to your input, people tend to take notice. And from the beginning this app was intended to save time when working with regular expressions so performance will always be a priority for me.

You can see the speed now by checking out the Regex Hero Tester. Don't blink. ;)


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.

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

Regex Analysis Bug Fixes

All of these updates relate to the analyzer, so if you're not a Regex Hero Professional user, then this won't affect you. I received a report of an analysis bug  related to character classes.  The regex analyzer wouldn't handle opening brackets inside a character class properly. It's one of the finer details of the regular expression syntax.  You wouldn't think that [[abc] would be valid, but it is.  You don't have to escape the opening bracket inside the character class.  So now the analyzer interprets this as it should. I've also fixed bugs around interpreting the \x00 (hex), \u0000 (unicode), and \k<group>  (backreference) expressions. P.S. The major updates I mentioned recently are still in the works.  So the price for Regex Hero Professional is still $20 for now.