[Mono-bugs] [Bug 76674][Maj] Changed - extremely poor performance and huge amount of memory consumption in case of extreme zooming

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Thu Dec 8 10:11:02 EST 2005

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by michael.paul at tao.es.


--- shadow/76674	2005-12-08 09:41:03.000000000 -0500
+++ shadow/76674.tmp.10412	2005-12-08 10:11:02.000000000 -0500
@@ -528,6 +528,56 @@
 ------- Additional Comments From michael.paul at tao.es  2005-12-08 09:41 -------
 Created an attachment (id=16189)
+------- Additional Comments From michael.paul at tao.es  2005-12-08 10:11 -------
+Yes, the problem still persists in the latest version of Mono and
+libgdiplus (1.1.0). 
+In order to compare, here is my system setup:
+Suse 10.0 (clean setup, including everything within Mono/CLR)
+installed mono-complete and gtk-sharp-2 with red-carpet today, latest
+versions as of 1.1.10,
+libgdiplus, monodoce-core, gecko-sharp2 and gtksourceview2 from
+official binary rpms for Suse 10.0
+With the help of this I recompiled everything needed to reproduce the
+problem using monoGIS. Please see the ShapeTest attachment.
+In order to reproduce, please do the following:
+- uncompress ShpTest.tar.gz with ordinary tar xvzf ShpTest.tar.gz,
+- compile the shapelib library for your system:
+  - do a tar xvzf shapelib-1.2.9.tar.gz
+  - cd into shapelib-1.2.9
+  - make lib
+  - make lib_install
+- change Main.cs (e.g. with vi) and update the line 21 to reflect your
+path, eg oReader.Open ("/home/mash/tests/data", ...), where ... means
+that this part shoud remain the same,
+- compile Main.cs: mcs /r:monoGIS.dll /r:System.Drawing Main.cs
+- if exist, delete shapes.rdx and Test.jpg files,
+- execute the program with different zoom levels:
+time mono Main.exe 10000:
+real    0m0.491s
+user    0m0.384s
+sys     0m0.092s
+time mono Main.exe 0.00003:
+real    0m0.817s
+user    0m0.296s
+sys     0m0.320s
+Timings seem OK? Nope!
+- now test, whether or not drawing of geometries is the problem
+- comment out line 34 of Main.cs (//oDevice.DrawGeometry..), 
+- execute again the test app, whatever zoom level you use timings will
+be very equal to those obtained in the first test (using a zoom level
+of 10000), although this test is drawing all states of Mexico. Whereas
+the performance bug occurs at extreme zoom levels where only two
+states have to be drawn.
+PD: if you need the source code of monoGIS for debugging purposes you
+may obtain it from http://sf.net/projects/mgis, file monoGIS-core-SRC.zip.

More information about the mono-bugs mailing list