I am fairly convinced that the performance slowdown in R# is MOSTLY due to the errors in the file. I have noticed a dramatic descrease in performnce for files which R# thinks there are errors (i.e. a lot of red or orange tick marks in the right hand column). If the file doesn't compile R# experiences a MAJOR performance decrease but once the error is corrected R# performance seems a lot better. I have seen files where total LOC > 10,000 and R# is fine because the file has a "GREEN" square at the top indicating there are no problems with it. I have also seen files where total LOC < 2,000 but that have a lot of tick marks on the right hand side. Even though the LOC is low, those files are impossible to edit if R# is turned on. I think this is where the big performance problems are:
(1) where there are a lot of tick marks
(2) When the error circle is blinking the performance degrades
(3) if there are any compile errors that are currently in the file - why is the file even analyzed if this is the case?
(4) when R# tries to fix indentation/parenthesis in files where there are compile problems - why is it trying to do that?
(5) when you have a lot of files open in VS -- why is R# trying to reparse other files? it should only reparse the file I am currently working on. If I only have 1 file open at a time in R# then performance is at its best.