|Do you know where your variables are?
Re^2: Efficient regex search on array tableby Polyglot (Chaplain)
|on Dec 15, 2022 at 05:35 UTC
Well, here are the almost-humorous results.
I was able to use the qr// on the output of the composeRegex subroutine--so the implementation was a cinch. After doing so, I found that my return times hovered around 11 or 12 seconds. I increased the regex complexity--almost no difference to the time. I began to have hope that something had really improved. To see how much difference it had made, I again removed the qr// from the subroutine's output and tried the identical query again....11 or 12 seconds--the same as before.
It was at this moment that I recalled having discovered a "wine" process running rampant and using cpu resources at full throttle earlier this morning, which I had killed, of course. Hah! Sluggish response just might have something to do with who else is hogging the cpu.
And as for MacOSX having a penchant for dependency on "wine," I say it's better to stay away from the inebriating stuff.
Unfortunately, in terms of breaking the 11-second barrier, that has not yet happened.