RE: Slow response in Visual Studio .NET 2003

All,

As has been the case with many of us, I feel that I've spent a
disproportionate amount of time dealing with IDE + Source Control
integration issues.  So instead of fighting (what I feel is) a losing
battle, my team and I have taken the following approach:

1.  Use SOS for our "Source Control Operations"
2.  Use VS.NET as our source code editor

What this means is that I'm "working disconnected".  When I want to
edit a file, I do so using SOS.  When I need to add a new file to my
VS.NET project, I check out the corresponding .csproj file (again using
SOS), and add the required file(s) using VS.NET (which updates the
.csproj file for me - as you know).  Sometimes VS.NET will complain and
ask me to check out a file which I've already checked out with SOS;
when this happens I go through the motions of "checking out" the file
in "disconnected" mode with VS.NET just to keep the IDE "happy". (Note:
 VSS apparently never "knows" about the VS.NET "check out" in this
instance; it (VSS) appears to "know"/"care" about only the SOS "check
out".)

The benefit of all this?  My solutions load quickly and I no longer
fear closing my IDE!

Regards,

Rob  

Disclaimer:  Don't nail me to the cross for any
errors/omissions/oversights - I'm simply suggesting a solution which
has worked for our team. 



--- "Perkins, Frank A." <[email protected]> wrote:
> IMO, there is a bug in SOS that's causing the IDE to be so slow.  If
> the
> client ran as slow as the IDE, I would concede that the internet was
> the
> bottleneck, but that's not the case.
>  
> I thought I was in the minority in having slowness issues with the
> IDE but
> it appears that several of SOS customers are having similar problems.
> Hopefully Sourcegear can add this as a priority to be fixed.
>  
> Frank
>  
> ----Original Message-----
> From: Alan Robertson [mailto:[email protected]] 
> Sent: Thursday, January 29, 2004 12:30 PM
> To: Luther Miller; [email protected]
> Subject: RE: [SOS-LIST] Slow response in Visual Studio .NET 2003
> 
> 
> 
> I think what defines bad performance is performance so poor that you
> have to
> alter your working methods to accomodate the integration with the
> IDE.
>  
> Since posting my last message I have duplicated the Solution and
> projects in
> their entirerty and posted them locally to our LAN. I have put them
> under
> source control using Visual SourceSafe. I swap between SCC providers
> depending whether I am connecting to the remote solution in the UK or
> the
> local. I first believed the the slowness using SOS in VS-2003 was
> partially
> due to the way VS tracked it files within source control  and the
> projects -
> possibly checking file existence or what not. But since moving this
> project
> locally and using VSS as my SCC provider the solution opens almost
> immediately and I can start working. Obviously I will concede the
> fact that
> the LAN is going to be immensly faster than an internet connection,
> but that
> being said SOS client is still pretty damn snappy itself. The only
> performance issue I have is specifacally using SOS within the IDE. As
> a test
> I also used SOS to test my local solution by connecting out through
> the
> internet and back in again to the server. I did see  a big
> performance hit
> again. I do not have any specifics as to time differences or
> anything. We
> are wrapping up a major project at the moment so I cannot pull away
> to test
> all the scenerios.
>  
> Alan
> 
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]]On Behalf Of Luther
> Miller
> Sent: Thursday, January 29, 2004 11:43 AM
> To: [email protected]
> 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 *  <http://www.softagon.com> 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:[email protected]] 
> Sent: Wednesday, January 28, 2004 8:29 PM
> To: Corey Steffen; [email protected]
> 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:[email protected]] 
> Sent: Wednesday, 21 January 2004 9:23 AM
> To: Alan Robertson; [email protected]
> 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: [email protected]
> [mailto:[email protected]
> <mailto:[email protected]> ]On Behalf Of Corey
> Steffen 
> 
> Sent: Monday, January 19, 2004 5:10 PM 
> 
> To: Alan Robertson; [email protected] 
> 
> 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
> 
> 


=====
Rob Reis | www.robreis.com | 415.860.9151 | Yahoo! IM:  wildreis | MSN Messenger:  wildreis