It goes up and the goes back down again... that is quite normal.<br><br>how big is your source table? memory use is relative the the source size..<br><br>if you table has lots of columns it will slow things down as MG does a select * from table so all the other columns
<br>which aren't needed are also returned... the Map 20 odd ADMP* columns can really exacerbate this.<br><br>One thing you can try is to generate a simplified version of your table... no need to use data at a 50mm resolution
<br>for a state map when one pixel is say equivalent to 50m on the ground.<br><br>The same data from SDF is rendered much faster than from oracle which makes the memory use less obvious<br><br><div class="gmail_quote">On Jan 23, 2008 9:40 AM, Maciej Skorczewski <
<a href="mailto:maciej.skorczewski@procad.pl">maciej.skorczewski@procad.pl</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
hi!<br><br>I use MG 1.2 + Oracle XE + MS Server 2003 + CPU Intel D 3 Ghz<br>when i use studio to get source and generate new layer from oracle<br>database source i see that MG process expand RAM from (normal) 40-70MB<br>to ...600MB and go up,and up...
<br><br>it is some bug? how many RAM should i have for this machine...it sounds<br>like never enough.<br><br>did you have this same problem?<br><br><br>maciek<br>_______________________________________________<br>mapguide-users mailing list
<br><a href="mailto:mapguide-users@lists.osgeo.org">mapguide-users@lists.osgeo.org</a><br><a href="http://lists.osgeo.org/mailman/listinfo/mapguide-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapguide-users
</a><br></blockquote></div><br><br clear="all"><br>-- <br>Zac Spitzer -<br><a href="http://zacster.blogspot.com">http://zacster.blogspot.com</a> (My Blog)<br>+61 405 847 168