RE: Slow response in Visual Studio .NET 2003

For our upcoming 4.0 release, we are putting effort into making the
IDE
faster.  Some improvements have already been made, and a few are
just
nearing completion.  We plan to do our final 4.0 preview release
next
week, and it should be stable enough to use for production code, so
I'd
be interested in knowing if it seems faster to everyone.

Corey Steffen
SourceGear LLC

At 11:25 AM 1/29/2004 -0800, Luther Miller wrote:

I should have mentioned this is with everything on the local LAN. I haven t been offsite in a while, but I don t recall much of a difference. In our case, IDE integration still provides more benefits and we rarely shutdown the IDE (I hibernate instead of shutting down, etc.) so it hasn t been a huge issue for me, but improvements would be welcome ;-)

 

_____________________________________________________________
Luther Miller " Managing Architect " MCSD (.NET)
Softagon Corporation " www.softagon.com
1 Pier Ste 1 " San Francisco, CA 94111
(415)733-9584 " (510)387-3490 cell " (415)394-9001 fax

---

From: Luther Miller
Sent: Thursday, January 29, 2004 8:43 AM
To: sos-list@xxxxxxxxxxxxxxxxxxxx
Subject: RE: [SOS-LIST] Slow response in Visual Studio .NET 2003

 

Marks brings up an interesting point.

What defines bad performance ? Perhaps its just whether or not the performance is bad enough to get a particular user to make any noise about it.

 

We didn t notice performance change much from VS.NET 2002 to VS.NET 2003.

 

We have a solution with about a dozen projects in it. To quote one of the developers on my team I ll do just about anything to avoid closing VS.NET and having to re-open the project.

 

We timed it on a couple of machines with different configurations (memory, hard drive, etc., but all machines that were purchased with in the last 18 months).

 

I started the timer when I opened the project, and quickly answered all dialogs, then waiting until I was at a point where I actually use the IDE. We timed this on two machines.

 

2 minutes and 30 seconds on one machine.

2 minutes and 15 seconds on another machine.

 

In any case, this is definitely not the performance we would like to have.

_____________________________________________________________
Luther Miller " Managing Architect " MCSD (.NET)
Softagon Corporation " www.softagon.com
1 Pier Ste 1 " San Francisco, CA 94111
(415)733-9584 " (510)387-3490 cell " (415)394-9001 fax

---

From: Mark A. Gregory [mailto:mgregory@xxxxxxxxx]
Sent: Wednesday, January 28, 2004 8:29 PM
To: Corey Steffen; sos-list@xxxxxxxxxxxxxxxxxxxx
Subject: RE: [SOS-LIST] Slow response in Visual Studio .NET 2003

 

Ho Hum, we have the same problem and so do everyone that I know who use SOS and .Net 2003.

 

I really dislike statements like only a small percentage of users have problem X .

 

Have you done a survey? What were the results?

 

The performance of SOS 3.5.3 with .Net 2003 is really poor.

 

EVERYONE has the problem, fix it in 3.5.3 please.

 

Mark

 

 

-----Original Message-----
From: Corey Steffen [mailto:corey@xxxxxxxxxxxxxx]
Sent: Wednesday, 21 January 2004 9:23 AM
To: Alan Robertson; sos-list@xxxxxxxxxxxxxxxxxxxx
Subject: RE: [SOS-LIST] Slow response in Visual Studio .NET 2003

 


There were no direct changes to the IDE Client for SOS 4.0 related to speed,
but I'd still be interested in knowing if 4.0 helps.  We've had other reports
of extremely bad performance in VS.NET 2003, but we've never been able to
reproduce the behavior ourselves and only a small percentage of our customers
seem to have the problem.  But I'd like to solve this for 4.0 if possible.

Corey

At 09:42 AM 1/20/2004 -0500, Alan Robertson wrote:

Hi Corey,
 
I have only 4 projects under my solution but of those 4 projects, 3 are just class files and very small only half a dozen files each. The main web project is close to 150 pages and numerous graphics as well. I have compared the files listed under source control within the SOS client to the files in the projects and they are the same so it all seems to function correctly together as far as getting the files into source control. "ALL" operations are signifigantly slower in Visual Studio. For instance when launching the SOS GUI, it automatically retriieves the file list from the server after login. that only takes about 20 seconds, in VS, that is also done but as it retrieves the file list it is also opening the project and takes about 10  - 12 minutes on average. If I do a get latest recursivly on the root of the files directory within the SOS Gui it takes on average two minutes or so to get all the latest files. If I do a get latest on the project root within VS it can take 20 minutes or so to complete. >From within VS checking 1 or two files out or in at a time is fast enough, but if I check in a couple of directories it can be rather slow as well.  To provide you with all the info, I am retrieving my files from a server in the United Kingdom, I am located in New Hampshire, USA. - But that would not explain the speed differences from the GUI to the IDE.
 
I received an email last night about the version 4 BETA, will this release address this speed issue? I would be happy to install it and try as long as there is not a chance of data corruption.
 
Thanks
Alan

-----Original Message-----

From: sos-list-admin@xxxxxxxxxxxxxxxxxxxx [mailto:sos-list-admin@xxxxxxxxxxxxxxxxxxxx]On Behalf Of Corey Steffen

Sent: Monday, January 19, 2004 5:10 PM

To: Alan Robertson; sos-list@xxxxxxxxxxxxxxxxxxxx

Subject: Re: [SOS-LIST] Slow response in Visual Studio .NET 2003

Hi Alan,

Approximately how many projects and files make up your solution which is

taking over 20 minutes to load?

When comparing the IDE's performance against the SOS GUI Client, are you

performing the operations recursively from the solution root folder?

Corey

At 02:22 PM 1/15/2004 -0500, Alan Robertson wrote:

We are currently using SOS 3.5.3 and visual studio.NET 2003 as the IDE. The response from within visual studio is incredibly slow when using it in conjuction with SOS. The project can take upwards of 20 to 30 minutes to open and retrieve the file list. If I "get latest" it can take over and hour at times to complete. When using the standalone SOS client these functions are signifigantly faster, only taking two to three minutes to complete. I have searched the list archives and have seen this question asked before, but without and answer be given.

 

This speed problem is quickly rendering SOS as an unacceptable choice to suit our needs. Please let me know if there is anything I can do to resolve this issue as soon as possible

 

Regards,

Alan Robertson