[mapguide-users] What is the best system specification for MG2.2 with 90ish layers?

[Zac Spitzer]

all sage advice!

using a combination of tiled an dynamic layers will help
always help with performance.

On Thu, May 31, 2012 at 6:16 PM, Gabriele Monfardini
<gabrimonfa at gmail.com> wrote:
>> Layers: 80ish (.shp, .tiff, Access database, SQL Express 2008)
>
> I think they are far too many.
> You will have slow map startup (even if most of them are not shown at
> startup, because of some per-layer overhead), and a very huge legend,
> that is probably a bit overwhelming for your users.
>
> I'm not saying that MGOS will be slow whichever resources you throw at
> it (it most depends on your data), it may results perfectly viable (or
> it may not).
>
> But I don't consider having a map that display so much layers a good approach.
>
> Moreover, you may want (if it is possible) to prepare your data.
> Using a database with a spatial index is the best solution, since your
> performance quickly become I/O bounded if you have huge tiff raster
> and shapefiles.
>
> You may consider loading shapefiles into a spatial layer of your db
> (though I'm not sure if and how you can do it in SQL Express), and
> loading Access data in SQL Express (and maybe connect data from MS
> Access if you need to access it from an external application). MS
> Access is not exactly tuned for performance, and you lack spatial
> indices.
>
> If you experience low performances and low CPU/memory load you may
> consider to move the db to another tier to mitigate I/O load.
> My 2 cents.
>
> Regards,
>
> Gabriele
> _______________________________________________
> mapguide-users mailing list
> mapguide-users at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapguide-users



-- 
Zac Spitzer
Solution Architect / Director
Ennoble Consultancy Australia
http://www.ennoble.com.au
http://zacster.blogspot.com
+61 405 847 168