3 ms·
Glancing at the stack traces with symbol server downloads enabled, it looks like there's a n^2 or potentially even exponential algorithm being run during the ch
by barrkel 10y ago
Glancing at the stack traces with symbol server downloads enabled, it looks like there's a n^2 or potentially even exponential algorithm being run during the checking phase - checks are run both passively and when actively applying. There's something very wrong with the design of the algorithm - it obviously doesn't scale. Bigger, fewer patches may simply be reducing the size of n.
IMO a better approach would be to offload the work to MS: upload a list of applied updates and let the cloud do the crunching. Much higher chance of memoizing and reusing work that way too. It's a sign of MS's client oriented culture still sticking around.