64-bit server creates a 32-bit app pool, what gives?

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
gsmalter
Posts: 115
Joined: Sat Jul 09, 2005 11:13 am

64-bit server creates a 32-bit app pool, what gives?

Post by gsmalter » Mon Jun 02, 2008 7:38 am

I just installed the brand new 64-bit version of Vault Server 4.1.2, and I let it create its own app pool (the default). But the app pool it created is set up to run in 32-bit mode. I thought the whole point of this new version was to run in 64-bit mode.

OS is Windows Server 2008.
Vault 5.0, Visual Studio 2010, Enhanced Client

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Mon Jun 02, 2008 9:44 am

You can change the Vault app pool to a 64-bit only app pool. All the .dlls in that get installed with the 64-bit installer are 64-bit so Vault will work without "allow 32-bit applications" turned on in IIS.
Mary Jo Skrobul
SourceGear

gsmalter
Posts: 115
Joined: Sat Jul 09, 2005 11:13 am

Works

Post by gsmalter » Mon Jun 02, 2008 10:06 am

That does work. So I guess the only problem is that it's kind of weird for the installer to set up a 32-bit app pool for a 64-bit installation.
Vault 5.0, Visual Studio 2010, Enhanced Client

mskrobul
Posts: 490
Joined: Wed Jan 14, 2004 10:22 am
Location: SourceGear
Contact:

Post by mskrobul » Mon Jun 02, 2008 10:17 am

It will be fixed it in the next release.
Mary Jo Skrobul
SourceGear

Thona
Posts: 18
Joined: Thu Mar 02, 2006 10:56 am

Don't

Post by Thona » Thu Jun 05, 2008 1:53 pm

Fixing this would break it. MS recommends running IIS application pools in 32 bit mode UNLESS there is a reason not to. Hosting guidelines recomment hosters to turn the application pools to 32 bit.

The reasons:
* You normally don't need more than the memory available in 32 bit
* The application uses less memory then.

I see both points valid for Vault.

gsmalter
Posts: 115
Joined: Sat Jul 09, 2005 11:13 am

Post by gsmalter » Thu Jun 05, 2008 5:08 pm

Taking some linear amount of additional memory in order to avoid the exponential decrease in performance that would occur if you hit the wall on available memory (even if you didn't know you'd need more memory than 32-bit gives you) is well worth it.
Vault 5.0, Visual Studio 2010, Enhanced Client

Thona
Posts: 18
Joined: Thu Mar 02, 2006 10:56 am

Post by Thona » Thu Jun 05, 2008 7:12 pm

Sadly it is not exacly THAT easy, given that we talk about garbage collected systems. Throwing memory at a problem that does not require memory in the first place is not smart.

I fail to see how a source control system that is not doing heavy assset storage (like video files) should ever require 2gb of memory.

jclausius
Posts: 3702
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear
Contact:

Post by jclausius » Fri Jun 06, 2008 7:08 am

Note, Vault was written to fit in the constraints of a 32-bit operating system. And we will continue to be very careful about memory consumption on the server.

However, limitations of IIS HTTP file uploads and the caching strategy for a very, very large number of files within a repository may be reason enough to run the Vault Server in 64-bit mode with more than 4GB of memory.
Jeff Clausius
SourceGear

Post Reply