[Mono-bugs] [Bug 397246] New: WinForms really slow on OSX
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Wed Jun 4 16:11:06 EDT 2008
https://bugzilla.novell.com/show_bug.cgi?id=397246
Summary: WinForms really slow on OSX
Product: Mono: Class Libraries
Version: 1.9.0
Platform: x86
OS/Version: Mac OS X 10.4
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Windows.Forms
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: atlas at spiralgraphics.biz
QAContact: mono-bugs at lists.ximian.com
Found By: Development
Created an attachment (id=220200)
--> (https://bugzilla.novell.com/attachment.cgi?id=220200)
Sample .NET application that runs slowly on OSX.
WinForms appear to be very slow on OSX. To see the problem you need a more
complex interface, such as the application provided in the attachment.
When I run application on a Vista machine with Core 2 Duo 2.0 Ghz, I experience
this:
1. Load exe. Main interface will paint instantly.
2. If a dialog pops up asking you to register application, just click "Later".
3. Click File > New. Interface will update instantly.
4. Click Create > Insert > Generator > Cells. Interface updates in about 0.3
seconds.
When I perform same steps on OSX 1.4 machine with Core Duo 1.6 Ghz (clean
system purchased only for Mono testing), I experience this:
1. Load exe. Main interface takes 18 seconds to finish refreshing.
2. If a dialog pops up asking you to register application, you must click
"Later". But on Mono the dialog may need to be enlarged before the "Later"
button becomes visible.
3. Click File > New. It takes about 12 seconds for the interface to finish
painting.
4. Click Create > Insert > Generator > Cells. It takes about 19 seconds for
interface to stop painting.
The OSX system used for testing is slower than the Vista system, but even my
old 1.8 Ghz Celeron XP machine beats the OSX machine by a factor of about 15x
when it comes to painting WinForms.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list