Infrequently Noted

Alex Russell on browsers, standards, and the process of progress.

Comments for Note To Self: Faster Chromium Builds (Updated)


"The last one is probably the most intractable."

Not 100% intractable, there's a big ass off switch:

find and rename feacp.dll to disable intellisense. For me, any value provided by that feature is nullified by its piss poor perf.

lloyd

by lloyd hilaiel at
Yeah, I've seen instructions on how to disable intellisense, but that's not what I'm gunning for. If I have to live without vs. having it suck, I'll have it suck. in a codebase as big as Chrome, it's an absolute life-saver.

What I want instead is a way to shut off scanning, schedule it, or make it work from a "read-only" database so that it stops slamming my disk when I'm trying to do other things. I know the VS team protests that intellisense does shut off when other CPU intensive things are going, but it's not a question of throughput, it's a question of latency. Intellisense making things laggy for any period of time is pretty much the cardinal sin in my mind.

Regards

by alex at