Hi Derhyk,

Thank you for your contacting us with this issue.
Since the performance of the Code Assistance functionality that can affect the typing process is improved in the latest TWS Spire R1 version, I kindly ask you to provide us with the next additional information related to the issue you are faced:

• Can you please tell me how many files includes your project when the issue is reproduced?
• Does issue apply for the coding process only or it is actual for the work of the IDE completely?

Our developers will investigate this issue. Any detailed information will help us in this.
Thank you,
Kate

Hi Kate,

Thanks for the post, answers below.

• When I right click to show the files in the project folder, it shows 1,304 files.


• As for the overall slowness, the coding was the most noticeable, opening debug logs seemed a bit slow as well, but I wasn't sure if that was normal behaviour - I can't recall the performance of debug logs in beta vs the new version.

--Derhyk

Hi Derhyk,



Thank you for your response.

We will include all these details to our investigation process.

I kindly ask you to answer one more question: does this issue apply to the Apex editor or for other editors also?



Thank you,

Kate

I can confirm that I see the same behavior in the last beta version of the software also for the current project I am working on, using the Windows version of TWS on a Windows 10 machine, I have 3713 files in the solution, with everything except reports and dashboards pulled down from Salesforce. Before I started turning things off, typing was like watching an old BBS load on a 2400 baud modem. I could actually type a sentence and then wait a few seconds for the entire sentence to slowly spell itself out.

I have turned off nearly every graphical propoerty of the editor. The thing that helped the most was under TOOLS | OPTIONS | TEXT EDITOR | ALL LANGUAGES | SCROLL BARS. I unchecked the "Show Annotations over vertical scroll bar" and set the Behavior setting on the same page to "Use bar mode for vertical scroll bar". That made a big differnce but it is still sluggish. I turned off line numbers, I turned off ALL Text Editor | Code Assistance features. Now the editor is liveable, but the editor still can't keep up with me typing, scrolling, or simply moving the cursor without a long delay in procesing.

I also tried turned off tracking the active file in the Solution Explorer and TOOLS | OPTIONS | VERSION CONTROL, LOcal Hisotry... those didn't seem to help any more

I run 5 copies of Visual Studio 2015 editing and debugging C# code at the same time on my machine, and never see slow behavior like this. Not a top of the line machine, but a very beefy machine.

Some VS2013 comments from Microsoft recommend disabling the Source Control plug-in for GIT, but that option is hidden from the TOOLS | OPTION page in TWS.

Hope this helps

Hi gtasker,



Thank you for such a detailed investigation and bug report!

May I please ask you to try working with the same files in the Spire R1 trial version? We have significantly modified the Code Assistance functionality and also have turned off part of the "search-as-you-type" feature as it was the reason of the performance issues for big files.

If you would try the Spire R1 version please let me know what is the result for you. In case if you would still experience any issues we will focus on them as a part of our work on the Code Assistance improvements.



Thank you,

Vladimir

Yes, I can give that a try tonight.

I should mention, if I close the solution that has 3700+ files in it, and open the exact same source file that was behaving badly in the solution, but as a single file, the response time while typing is instantaneous, and scrolling and caret movement within the editor also show no delays.

I just finished testing the Spire R1 install with the exact same scenarios I described above that were showing such slow response times, and wow what a difference! 3700+ files in the solution and with nothing disabled, all the functionality that was slow is now instant. In fact, FIND IN FILES which I hadn't mentioned earlier, was processing one file every 2-3 seconds...with Spire R1, FIND IN FILES checked my entire solution in less than 2 seconds.

I have 30 days on this trial, I'll report back if the behavior deteriorates again.

Hi gtasker,



Thank you for an update - this is a great news! Hope you'll enjoy Spire R1 :) We will also release Spire R2 with a couple of bugfixes today or tomorrow.

Please let us know if you'll have any comments regarding the Spire version.



Thank you,

Vladimir