Current filter:
                                You should refresh the page.
                                0
                                Judith Estep 12.26.2012

                                  • I just upgraded from 2. (don't remember exactly, but it was .1 or .01) and parsing the solution items is taking quite a bit longer than it did in the older version.
                                    Is there anything specific I need to do?
                                    Thanks

                                Show all comments
                                • Alex Skorkin (DevExpress Support) 12.27.2012

                                  Hi Judith,

                                  You do not need to do anything specific. Would you please provide more information on your solution? How big is it? How many projects does it have? What kind of projects does it contain? The first time you open a solution, it may take a lot of time to be parsed. However, every next opening will take less time as the caching mechanism is used instead on the next solution load.

                                • Judith Estep 12.27.2012

                                  I have numerous solutions which are similar. They are web sites with around 300-400 files. I just opened one up that I had opened yesterday and it tool 92 seconds for the parsing solution task to get done and unlock the files so I could work on them.
                                  Other info- I do have the sites under Subversion.
                                  CPU for deveng goes up to about 85%, then drops down once solution is parsed.
                                  I had a similar problem with Visual SVN when I upgraded to VS 2012- it locked VS as it was doing it's thing. That is what happens now. Here is what they found out- maybe it is something similar. It just didn't take as long before I upgraded DevExpress, even though I was still using VS 2012.
                                  https://connect.microsoft.com/VisualStudio/feedback/details/765880

                                • Alex Skorkin (DevExpress Support) 12.27.2012

                                  Thank you for the update, Judith.

                                  We have a special diagnostic tool included in the product that may help us research the performance issue when your solution is parsed.

                                  You are welcome to refer to the following Knowledge Base article and collect the required diagnostic log files:

                                  What is the best way to track down the cause of the performance problems?

                                  You may not select all the options, but only the 'Parser profiling' option.

                                • Judith Estep 12.27.2012

                                  Here are the logs.
                                  Thanks

                                  Log.zip
                                • Alex Skorkin (DevExpress Support) 12.28.2012

                                  Hi Judith,

                                  Thank you for providing the log files. I have reviewed them with a special tool and found only the following operation that takes abnormal time for processing:

                                  Event handler: CR_UnitTestRunner.UnitTestService.EventNexus_SolutionParsed
                                  Work time: 65.39 sec
                                  Allocated memory: 12.1 MB

                                  This operation is related to the Unit Test Runner service. Once a solution is parsed, it took more than 1 minute to be processed. I recommend you temporarily disable this service in the CodeRush Options Dialog accessible via the DevExpress menu on the Unit Testing | Test Runner option page (Enable Unit Tests Service) and see if it makes a difference. What are your results?

                                • Judith Estep 12.28.2012

                                  Thanks, that fixed it. It took only about 10 seconds on a solution I used yesterday and didn't lock the screen up while I was waiting.

                                Show all comments
                                Leave a Comment
                                You must  log in  or  register  to leave comments

                                1 Solution

                                1
                                Alex Skorkin (DevExpress Support) 12.29.2012

                                Hi Judith,

                                This is great news! I'm glad to hear that it works faster for you now. However, we are going to look into our Unit Test Runner service and see why it took a lot of time to process a solution.

                                And just a quick note for everyone experiencing this issue:

                                If a solution build process takes longer than expected, try to disable the Unit Test Service and see if it makes a difference. The Unit Test Service is configurable on the Unit Testing | Test Runner option page (Enable Unit Tests Service) in the CodeRush Options Dialog (accessible via the DevExpress menu).

                                Leave a Comment
                                You must  log in  or  register  to leave comments
                                You must  log in  or  register  to leave an answer

                                Is your intention to post an answer to your own question?

                                • If so, then proceed.
                                • If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
                                • If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.