[mapserver-users] 64 bit Windows OS

Bruce Cheney BLC at JUB.com
Tue Oct 28 13:29:40 EDT 2008


Tamas,

We had come to the same conclusion, to use the approach in #1 on your
list of recommendations.  With a future attempt at moving to 64 bit.
Thanks for your great help.  It is good to know the trouble spots in
trying to compile dependencies to 64 bit.  


Bruce Cheney
Gateway Mapping, Inc
www.gatewaymapping.com
801.221.7656

-----Original Message-----
From: mapserver-users-bounces at lists.osgeo.org
[mailto:mapserver-users-bounces at lists.osgeo.org] On Behalf Of Tamas
Szekeres
Sent: Tuesday, October 28, 2008 8:44 AM
To: Bruce Cheney
Cc: mapserver-users at lists.osgeo.org
Subject: Re: [mapserver-users] 64 bit Windows OS

Bruce,

If you'd run your application in 32 bit mode (by using 32 bit
binaries) you can consider the following options:

1. If you are using IIS6 (Windows Server 2003) you cannot run 32 bin and
64 bit applications simultaneously. You can force to execute IIS in 32
mode globally according to http://support.microsoft.com/kb/894435/en-us
In this case you might also force the compilation of your application to
32 bit by specifying the platform target to x86, something like:
<%@ Page Language="C#" ... CompilerOptions="/platform:x86" %>

This can be specified in the application web.config file as well.


2. If you are using IIS7 the 32 bit and 64 bit ASP.NET applications can
be run side by side. For more information in this topic refer to the
following article:
http://blogs.msdn.com/rakkimk/archive/2007/11/03/iis7-running-32-bit-and
-64-bit-asp-net-versions-at-the-same-time-on-different-worker-processes.
aspx
In this case you'll also have to set CompilerOptions="/platform:x86 with
your application.


With regards to the 64 bit path all of the dependencies have to be
compiled for x64 then. You might have to consider which features should
be included in the compilation many of the dependencies can be compiled
fairly well, however for some of the drivers like SDE I couldn't obtain
the proper version of the .lib and .dll files to accomplish this task.

Best regards,

Tamas



2008/10/28 Bruce Cheney <BLC at jub.com>:
> Thank you Tamas and Frank.  I believe that effectively answers my 
> questions.  We are running C#, ASP.Net on a Win64 machine so the setup

> requires (or would best be suited for) a 64bit version. In the stated 
> situation the 32 bit version does not work. So we may leave the 
> machine in 64 bit and set the site to 32 bit in IIS or venture down 
> the path of building all the libraries for 64 bit. If we switch the 
> site to 32bit we may then be able to use the extra RAM through the OS
as overflow.
>
> In venturing down the 64 bit path I am most concerned about all the 
> supporting libraries being converted/compiled for 64bit. If this is 
> laborious as you say then I also would assume it means it requires 
> enough knowledge to get all the ducks lined up correctly.  This path 
> may be one for me to venture down during a significantly large 
> development cycle - if ever.
>
> With the direction of all new hardware being 64 bit will the standard 
> distribution of mapserver become also 64 bit?  Unless in a majority of

> situations it just doesn't make any difference.
>
>
> Bruce Cheney
> Gateway Mapping, Inc
> www.gatewaymapping.com
> 801.221.7656
>
> -----Original Message-----
> From: mapserver-users-bounces at lists.osgeo.org
> [mailto:mapserver-users-bounces at lists.osgeo.org] On Behalf Of Frank 
> Warmerdam
> Sent: Monday, October 27, 2008 6:27 PM
> To: Bruce Cheney
> Cc: mapserver-users at lists.osgeo.org
> Subject: Re: [mapserver-users] 64 bit Windows OS
>
> Bruce Cheney wrote:
>>
>> What are the current plans for supporting 64 bit Windows OS?
>> Already doing it and I missed it?
>> What would be reasons for not actively pursuing this?
>> Are some of the supporting binaries to difficult to convert over or 
>> MapServer itself?
>> Is it the challenge of maintaining two paths 32 bit and 64 bit?
>
> Bruce,
>
> I believe MapServer and it's supporting libraries can already be 
> somewhat laborously built for Win64.  There is no fundamental problem 
> with the software that would make it incompatible.
>
>> The reasons I am asking are:
>>
>> Hardware and OS are coming this way now - 64 bit. We must go to some 
>> effort to downgrade to 32 bit.  The 64 bit obviously supports more
> RAM.
>> More RAM = more concurrent users.  And there are probably other good 
>> reasons that I am at a loss to remember.
>>
>> Thanks for any wisdom you might have in this regards.
>
> Honestly, a single instance of mapserver will not often make effective

> use of more than 2GB of in process memory except for special 
> activities (like render super-tile sized images).  You will however 
> get significant benefit from having alot of RAM on a 64bit system even

> if you only have 32bit mapserver's since the operating system can 
> effectively cache more material from disk.
>
> Best regards,
> --
> ---------------------------------------+------------------------------
> ---------------------------------------+--
> ---------------------------------------+------
> I set the clouds in motion - turn up   | Frank Warmerdam,
> warmerdam at pobox.com
> light and sound - activate the windows | http://pobox.com/~warmerdam
> and watch the world go round - Rush    | Geospatial Programmer for
Rent
>
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
> _______________________________________________
> mapserver-users mailing list
> mapserver-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-users
>
_______________________________________________
mapserver-users mailing list
mapserver-users at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/mapserver-users


More information about the mapserver-users mailing list