Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
I am attaching a simple multi-threaded application that performs work on large collections of strings. On Windows and Linux I can easily use it with a string containing 150K lines but on the Mac due to performance constraints I have not been able to use it with large amounts of data. On dual core machines with 4 GB of RAM and processing only 15,000 lines here are the processing times:
Windows - 46 seconds
Linux - 22 seconds
Macintosh - 3,944 seconds
Can something be done to improve the processing time on Mac? This is for a product my company will be selling and right now I don't think we can even offer it for the Mac due to the performance. Thank you!
Created attachment 4805 [details]
This is not a Xamarin.Mac project. If you can recreate the test case as a console project (does not rely on Windows Forms (we do not support Windows Forms on Mac)), we can take a look.
I suspect that the performance issue might actually be related to the Windows Forms implementation itself, not Mono in general. Again, we do not support or recommend using Windows Forms on Mac, at all. In fact, it took 30 seconds for the test window to even display on screen.
Closing as invalid for now. Please re-open if you can recreate the performance issues outside of the context of Windows Forms.
Created attachment 4999 [details]
Test case with windows forms removed (27 seconds for 15k lines)
I've attached a modified test case that uses your "MainDriver" and "StringTransformationWorker" in a console project.
The running time for processing 15,000 strings on my OS X machine is on par with the time for Mono on Linux that you reported: 27 seconds (4 cores, 2.9 GHz Core i7, 8GB RAM).