Code Compare starts very slow, normal?

Discussion of open issues, suggestions and bugs regarding file and folder merge tool – Code Compare
privatepyle
Posts: 14
Joined: Wed 25 Feb 2015 09:37

Re: Code Compare starts very slow, normal?

Post by privatepyle » Thu 19 Mar 2015 15:42

Well then, let's see how fast Compare++ is starting. Maybe they have other priorities.

privatepyle
Posts: 14
Joined: Wed 25 Feb 2015 09:37

Re: Code Compare starts very slow, normal?

Post by privatepyle » Wed 12 Aug 2015 09:52

Are there any news here? Our subscription is up for renewal, but at that speed it ain't of any use...

If there isn't a solution within a month, then we'll switch to Compare++

flobergs
Posts: 4
Joined: Tue 31 Oct 2017 13:20

Re: Code Compare starts very slow, normal?

Post by flobergs » Thu 02 Nov 2017 10:43

We are using current version of Code Compare and expericensing this issue/problem, that opening comparison window takes long.

1.) We want to use Visual Studio integrated Code Compare window, but with current version it takes too long opening/starting a comparison, with a wait time from 5 to 10 seconds on a state of the art development machine. We also tried switch "Prevent Code Compare closing", but it does not help here. dotTrace-performance analyzation states that you loose at least 2 seconds alone only in your code when calling Devart.FileCompare.MemoryTrackService.CheckMemory(FileCompareUnit unit) from Devart.FileCompare.FileCompareUnit.CreateComparableHost()...

flobergs
Posts: 4
Joined: Tue 31 Oct 2017 13:20

Re: Code Compare starts very slow, normal?

Post by flobergs » Thu 02 Nov 2017 10:48

(As additon to my previous post) Please note that allmost all execution time of CheckMemory is wasted for "garbage collection", as dotTrace-performance-analysis measured.

mstislavs
Devart Team
Posts: 101
Joined: Mon 16 Jan 2017 12:48

Re: Code Compare starts very slow, normal?

Post by mstislavs » Tue 07 Nov 2017 13:04

flobergs wrote:We are using current version of Code Compare and expericensing this issue/problem, that opening comparison window takes long.

1.) We want to use Visual Studio integrated Code Compare window, but with current version it takes too long opening/starting a comparison, with a wait time from 5 to 10 seconds on a state of the art development machine. We also tried switch "Prevent Code Compare closing", but it does not help here. dotTrace-performance analyzation states that you loose at least 2 seconds alone only in your code when calling Devart.FileCompare.MemoryTrackService.CheckMemory(FileCompareUnit unit) from Devart.FileCompare.FileCompareUnit.CreateComparableHost()...
Thank you for reporting the performance issue. Please provide us the files with which the issue reproduces using the following form:
https://www.devart.com/company/contactf ... odecompare

Best regards,
Mstislav Sakidon
Devart Team
www.devart.com

justdev
Posts: 1
Joined: Thu 28 May 2020 08:57

Re: Code Compare starts very slow, normal?

Post by justdev » Thu 28 May 2020 09:11

Same showstopper issue here: CC 5.3.231 (latest), integration with VS2019 (compare inline in IDE), very powerful computer and on a tiny project the DIFF action takes at least 5 secs to open code compare window. In code compare`s settings, there is no suggested 'Prevent code compare closing' option but 'Prevent Visual Studio closing' and it`s checked.

Is there any way to fix this?

ekaterinag
Devart Team
Posts: 23
Joined: Wed 06 Nov 2019 06:48

Re: Code Compare starts very slow, normal?

Post by ekaterinag » Mon 01 Jun 2020 08:43

Hi. There could be delays in Visual Studio since Code Compare uses full documents with all functionality of Visual Studio, also delays may be caused by other extensions integrated into the documents.
Do you require intellisense for comparison?

Post Reply