Slow...can we bypass the web service?

neal007 · Post by **neal007** » Mon Feb 23, 2004 6:17 pm

Hello,

I'm a little concerned (first look) that this is slower then VSS. I use an intranet so I don't know why I need to go through a web service if it may be faster with a direct connect mode.

Thoughts?

ericsink · Post by **ericsink** » Mon Feb 23, 2004 7:47 pm

neal007 wrote:Hello,

I'm a little concerned (first look) that this is slower then VSS. I use an intranet so I don't know why I need to go through a web service if it may be faster with a direct connect mode.

Thoughts?

If Vault seems slow, we always want to hear more details. Sometimes the problem is simply a configuration issue.

No, there is no way to bypass the web service layer. Doing so is unnecessary anyway. The Web Service layer is not the performance problem that you might think.

neal007 · Post by **neal007** » Mon Feb 23, 2004 7:51 pm

It seems to be the initialization within VS.NET 2003. I wonder if it's also the app in IIS after not being used is recycling/sleeping, then needs to recompile after not using after XX hours? May be a function of ASP.NET, something VSS doesn't have to deal with.

ericsink · Post by **ericsink** » Mon Feb 23, 2004 8:21 pm

neal007 wrote:It seems to be the initialization within VS.NET 2003. I wonder if it's also the app in IIS after not being used is recycling/sleeping, then needs to recompile after not using after XX hours? May be a function of ASP.NET, something VSS doesn't have to deal with.

You're using the IDE integration client, then? What version of Vault?

neal007 · Post by **neal007** » Mon Feb 23, 2004 8:26 pm

Version 2.

Vault is running on a Windows 2003 Standard Server. I'm dev'ing on a Windows XP Pro system connecting to Windows 2003 / Vault via 100mbit LAN.

ericsink · Post by **ericsink** » Mon Feb 23, 2004 8:43 pm

neal007 wrote:Version 2.

Vault is running on a Windows 2003 Standard Server. I'm dev'ing on a Windows XP Pro system connecting to Windows 2003 / Vault via 100mbit LAN.

OK, so just to be clear: You're saying it takes a long time to open your solution file? How many projects are in it? How long does it take?

neal007 · Post by **neal007** » Mon Feb 23, 2004 8:51 pm

Yes, when I wake up tomorrow and get to work, I see the "Initializing Vault" dialog, then it opens the project, which is a asp.net web solution with maybe five projects within. I also see this with smaller solutions (less projects). Subsequent use is much faster.

neal007 · Post by **neal007** » Mon Feb 23, 2004 8:52 pm

Sorry, forgot the time you asked for. I'd say 30-60 seconds to load up, when using VSS it was half that or less.

ericsink · Post by **ericsink** » Mon Feb 23, 2004 9:12 pm

neal007 wrote:Sorry, forgot the time you asked for. I'd say 30-60 seconds to load up, when using VSS it was half that or less.

Just curious: Do you have folder security turned on for your repository? We found a bug which can slow things down rather badly when this is turned on. (I think the problem will be fixed in 2.0.1, BTW.)

neal007 · Post by **neal007** » Mon Feb 23, 2004 9:21 pm

What do I look for to see if this is the case?

ericsink · Post by **ericsink** » Mon Feb 23, 2004 9:27 pm

neal007 wrote:What do I look for to see if this is the case?

It's in the Vault Admin tool. I *think* it's in the repositories tab. Click to see the repository properties, and it will show you a checkbox.

I don't have Vault handy, so I can't verify this.

neal007 · Post by **neal007** » Mon Feb 23, 2004 9:44 pm

Folder security is/was not checked.

ericsink · Post by **ericsink** » Mon Feb 23, 2004 10:04 pm

neal007 wrote:Folder security is/was not checked.

OK. In some cases, Vault is faster than VSS. In other cases, it is slower. It looks possible that your usage falls into the latter category.

There is another thing or two you could check:

Make sure your Vault server is configured NOT to do reverse DNS lookups. Once again, I think this is in the Vault admin tool.

Make sure your VaultService directory is configured for anonymous access.

neal007 · Post by **neal007** » Mon Feb 23, 2004 10:10 pm

Okay, I'll check. But wouldn't it make more sense for performance if we directly connected to the SQL Server instead of via a web service? Just wish I didn't have to go through IIS / Web Services to get to my data that's essentially local to my dev computer (via internal LAN).

ericsink · Post by **ericsink** » Mon Feb 23, 2004 10:31 pm

neal007 wrote:Okay, I'll check. But wouldn't it make more sense for performance if we directly connected to the SQL Server instead of via a web service? Just wish I didn't have to go through IIS / Web Services to get to my data that's essentially local to my dev computer (via internal LAN).

I assume we just changed the subject from "helping you resolve a problem" to "brainstorming the right way to rewrite Vault".

You suggest moving all of the logic in the Vault server over to the client, which will talk directly to SQL Server. I'll admit that's an interesting set of things to think about, but it's a radically different design.

In any case, remote access is a very important part of Vault, so we would still need the entire HTTP path anyway.

Furthermore, I will maintain my assertion that going through IIS isn't costing very much, although I can't prove that empirically.

BTW, I think the real cost of using IIS is not performance but the hassle of installation and the additional tech support troubles which comes from all the various configuration problems with ASP.NET. All technology choices involve tradeoffs.

SourceGear Support

Slow...can we bypass the web service?

Slow...can we bypass the web service?

Re: Slow...can we bypass the web service?