Which sorting algorithm is used by .NET's Array.Sort() method?
-
Related thread related to stability of the algorithm used by sort method.RBT– RBT2017-08-27 09:35:08 +00:00Commented Aug 27, 2017 at 9:35
-
Related thread: When you use LINQ based sorting instead.RBT– RBT2017-08-27 09:36:32 +00:00Commented Aug 27, 2017 at 9:36
7 Answers
Array.Sort() chooses one of three sorting algorithm, depending on the size of the input:
- If the size is fewer than 16 elements, it uses an insertion sort algorithm.
- If the size exceeds
2 * log^N, whereNis the range of the input array, it uses a Heap Sort algorithm. - Otherwise, it uses a Quicksort algorithm
Source: Array.Sort(Array) Method on MSDN.
2 Comments
Array.Sort implements Introsort, which is designed to use Quicksort in most cases (with the added optimization of using Insertion sort for small partitions), but if it detects that the item ordering results in a pathological case for Quicksort, it changes to Heapsort.Actually, It's not that easy as it's seems. It looks like .NET is implementing a set of different sorting algorithms depending on the input and his size. I used to decompile Array.Sort() from CLR and it seems that they are using both Heap, Insertion and Quicksort. 
2 Comments
Some more notes from MSDN
This method uses the introspective sort (introsort) algorithm as follows:
If the partition size is fewer than 16 elements, it uses an insertion sort algorithm.
If the number of partitions exceeds 2 * LogN, where N is the range of the input array, it uses a Heapsort algorithm.
Otherwise, it uses a Quicksort algorithm.
This implementation performs an unstable sort; that is, if two elements are equal, their order might not be preserved. In contrast, a stable sort preserves the order of elements that are equal.
For arrays that are sorted by using the Heapsort and Quicksort algorithms, in the worst case, this method is an O(n log n) operation, where n is length.
Notes to Callers The .NET Framework 4 and earlier versions used only the Quicksort algorithm. Quicksort identifies invalid comparers in some situations in which the sorting operation throws an IndexOutOfRangeException exception, and throws an ArgumentException exception to the caller. Starting with the .NET Framework 4.5, it is possible that sorting operations that previously threw ArgumentException will not throw an exception, because the insertion sort and heapsort algorithms do not detect an invalid comparer. For the most part, this applies to arrays with fewer than 16 elements.
Comments
4 Comments
Quick sort as mentioned. But it does not equally well for all data!
By using reflector: it does sort in a native dll -> for the most common case of 1D arrays, ascending order. However, other cases are sorted in managed code - with very little optimizations applied. Hence their speed is usually much slower.
1 Comment
It really uses the Introsort algorithm, which is a hybrid sorting algorithm, consisting of the following:
- Insertion sort
- Heapsort
- Quicksort
The performance is O(n log n) in the average/worst cases. Introsort is in-place (doesn't require lots of RAM) and non-stable (can't predict the order of equal elements) algorithm
From MSDN
This method uses the introspective sort (introsort) algorithm as follows:
If the partition size is less than or equal to 16 elements, it uses an insertion sort algorithm.
If the number of partitions exceeds 2 * LogN, where N is the range of the input array, it uses a Heapsort algorithm.
Otherwise, it uses a Quicksort algorithm.