Mono 3.8 release: further performance improvement and scalability improvement, mono3.8

Mono 3.8 release: further performance improvement and scalability improvement, mono3.8

Mono 3.8.0 was released on September 10, September 4. The runtime of this version brings some performance and scalability improvements, and completes the migration to the Windows platform.

Mono follows the Gnome and Linux kernel version numbering policies, meaning that 3.8 is a major stable version after 3.6 (released last month. This version improves performance:

• JIT can better deal with the remainder operation of the long type with the power of divisor 2, and the generated code is much better. Previously, the remainder operation of the long type will not be treated as special as that of the int type. (As a compilation optimization, the multiplication and division operations of power 2 are usually replaced by shift operations .)
• For a delegate that only calls once, you can generate faster code. This is of great help for the C # feature delegated to underlying layers such as async and LINQ.
• There is a new hashtable that can be concurrently read at runtime, which helps improve scalability.
• GC time is reduced by 5-10%.

The Community is excited about the continuous performance improvement of one version of Mono. Richard Simpson concluded that:

The version released by the Mono team is really impressive. What impressed me the most about Mono is performance.

This version also has some improvements in debugging, especially USB debugging. Considering that cross-platform mobile development is a major use case of Mono, this improvement is very popular. Debugging a wired protocol can now better handle high latency situations. The client library will also aggressively cache more information. This reduces the number of packages to be transferred and reduces debugging latency. When Xamarin is used for cross-platform mobile development, this double change will bring a better debugging experience.

In addition, there are many Bug fixes, including runtime, class libraries, C # compilers, MSBuild, and debuggers, which improve the overall stability and performance. The release description details all the modifications. For more information, see.

Mono 3.6 does not support all platforms, especially Windows and non-Debian Linux variants. Mono 3.8 supports more Linux variants. As mentioned in the release notes, porting to Windows 64 has also been completed. However, the Mono website does not provide Windows Installation programs. We must build the latest binary files from the source code.

Mono is a project funded by Xamarin and is an open-source implementation of Microsoft's. NET Framework. It makes cross-platform development possible using C #, F #, and other. NET languages. Xamarin builds a cross-platform development tool and a framework product such as Xamarin. Forms (cross-platform code can be used to assist in creating native experiences) on Mono. Development tools and frameworks have applications among developers (Xamarin recently received $54 million in C round financing and will continue to work in this area ). Xamarin is also working with Microsoft to improve compatibility between. NET and Mono. ASP. NET vNext (especially KRuntime) is one of the achievements of this cooperation. It can run well in. NET and Mono runtime.

View Original English text:Mono Gets Further Performance, Scalability Improvements

View Original Chinese Text: Mono 3.8 release: further performance improvement and scalability Improvement

What is algorithm scalability?

My personal understanding is that algorithms have good performance in processing data of all sizes. As the data increases, the efficiency will not decrease quickly.

Q: What does "oracle portability and scalability" mean?

1. Portability: oracle can provide good cross-platform performance. oracle databases on windows can be easily transplanted to linux, data can be used in the past), and vice versa. Other databases, such as SqlServer, can only be used on windows.

2. Scalability: refers to the database performance. When one person accesses the database and 1000 or even 10 thousand or more people access the database, by setting databases (adding servers when there are too many people and removing servers when there are few people), the performance will not be much different and the performance will be similar. This is scalability.

---
The above is helpful to you.