Multithreading processing?

[Tim Smith]

On Apr 22, 2010, at 7:44 PM, alexandru wrote:
>> On Apr 22, 2010, at 1:46 PM, Greg Ward wrote:
>>> At a certain scale, CPU speed starts to matter in certain operations.
>>> E.g. for us "hg status" is CPU bound because we have to test tens of
>>> thousands of filenames against a huge regex.  (No, I haven't tried
>>> inotify... it's on my list!)
>> 
>> Couldn't much of this be cached, so it's only slow the first time?
> 
> I'm likely missing something, but which part would you consider for caching? 'status' is the command one would use when it's telling Mercurial to refresh it's knowledge of the world, so wouldn't a cache be effectively stale every time one runs 'status' (or, alternatively, 'status' would miss changes because it would look at the cache?)

I'm just talking about the matching filenames against a regular expression part. Whether a given filename matches the regular expression or not won't change unless the regular expression changes. How often does the regular expression change?

-- 
Tim Smith