[mapguide-users] Re: MgCooker performances

[Zac Spitzer]

I would suggest on a four core machine, perhaps 8 concurrent requests,
depending on how heavy your map is to render.

anything running in a VM is also going to be a bit slower than a non virtualised
machine, especially whilst running a cpu intensive application

you just need to experiment to see which config ends up driving the
load at close to 100% cpu.

ignore the time estimate and focus on the tiles remaining / throughput,
the current time esitimate reminds me of "microsoft minutes" whilst copying
lots of files.

also mgcooker defaults to 1 concurrent request which means you are
tiling a single tile at a time, which obviously is the slowest approach
available.

z


On Tue, Apr 24, 2012 at 12:50 PM, Jackie Ng <jumpinjackie at gmail.com> wrote:
> Besides adaptation to newer Maestro APIs, the core tile generation logic in
> MgCooker has not changed since the very first release (before I started on
> it).
>
> The estimation is obviously wrong. I just can't tell you where at the
> moment.
>
> - Jackie
>
> --
> View this message in context: http://osgeo-org.1560.n6.nabble.com/MgCoocker-performances-tp4911616p4912237.html
> Sent from the MapGuide Users mailing list archive at Nabble.com.
> _______________________________________________
> 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