.net中的字符串操做性能問題由來已久,幸運的是微軟推出了span<T>高性能指針操做封裝工具類。這個類到底有多高的性能呢?網上傳言反正很高,可是實際上在網上很難找到合適的測試實例,這讓本人實在無力吐槽。經不住高性能這三個字的誘惑,本人仍是瞭解了一番後作了幾個簡單樣例來測試一番,下面列出幾種字符串常見操做的測試代碼及其運行結果。工具
1、String.Index 測試性能
1 var t1 = StopWacherHelper.DoTimer(() => 2 { 3 for (int i = 0; i < count; i++) 4 { 5 str.IndexOf(subStr); 6 } 7 }); 8 9 Console.WriteLine($"string.IndexOf {count} 次用時:{t1} 毫秒");
1 var t2 = StopWacherHelper.DoTimer(() => 2 { 3 var strSpan = str.AsSpan(); 4 5 var subStrSpan = subStr.AsSpan(); 6 7 for (int i = 0; i < count; i++) 8 { 9 strSpan.IndexOf(subStrSpan); 10 } 11 }); 12 13 Console.WriteLine($"Span<T>.IndexOf {count} 次用時:{t2} 毫秒");
2、String.Substring 測試測試
1 var t1 = StopWacherHelper.DoTimer(() => 2 { 3 for (int i = 0; i < count; i++) 4 { 5 str.Substring(0, str.IndexOf(subStr)); 6 } 7 }); 8 9 Console.WriteLine($"String.Substring {count} 次用時:{t1} 毫秒");
1 var t2 = StopWacherHelper.DoTimer(() => 2 { 3 var strSpan = str.AsSpan(); 4 5 var subStrSpan = subStr.AsSpan(); 6 7 var index = strSpan.IndexOf(subStrSpan); 8 9 for (int i = 0; i < count; i++) 10 { 11 strSpan.Slice(0, strSpan.IndexOf(subStrSpan)); 12 } 13 });
3、String.Split 測試spa
1 var t1 = StopWacherHelper.DoTimer(() => 2 { 3 for (int i = 0; i < count; i++) 4 { 5 var arr = str.Split(new string[] { splitStr }, StringSplitOptions.None); 6 } 7 }); 8 9 Console.WriteLine($"String.Split {count} 次用時:{t1} 毫秒");
1 var t2 = StopWacherHelper.DoTimer(() => 2 { 3 var strSpan = str.AsSpan(); 4 5 var splitSapn = splitStr.AsSpan(); 6 7 int m = 0, n = 0; 8 9 for (int i = 0; i < count; i++) 10 { 11 List<string> arr = new List<string>(); 12 13 while (true) 14 { 15 m = n; 16 n = strSpan.IndexOf(splitSapn); 17 if (n > -1) 18 { 19 arr.Add(strSpan.Slice(0, n).ToString()); 20 strSpan = strSpan.Slice(n + splitSapn.Length); 21 } 22 else 23 { 24 break; 25 } 26 } 27 28 } 29 }); 30 31 Console.WriteLine($"Span<T>.Split {count} 次用時:{t2} 毫秒");
4、String.Replace 測試.net
1 var t1 = StopWacherHelper.DoTimer(() => 2 { 3 for (int i = 0; i < count; i++) 4 { 5 str.Replace(splitStr, replaceStr); 6 } 7 }); 8 9 Console.WriteLine($"String.Replace {count} 次用時:{t1} 毫秒");
1 var t2 = StopWacherHelper.DoTimer(() => 2 { 3 var strSpan = str.AsSpan(); 4 5 var splitSapn = splitStr.AsSpan(); 6 7 int m = 0, n = 0; 8 9 for (int i = 0; i < count; i++) 10 { 11 List<string> arr = new List<string>(); 12 13 while (true) 14 { 15 m = n; 16 n = strSpan.IndexOf(splitSapn); 17 if (n > -1) 18 { 19 arr.Add(strSpan.Slice(0, n).ToString()); 20 strSpan = strSpan.Slice(n + splitSapn.Length); 21 } 22 else 23 { 24 break; 25 } 26 } 27 string.Join(replaceStr, arr); 28 } 29 }); 30 31 Console.WriteLine($"Span<T>.Replace {count} 次用時:{t2} 毫秒");
怎麼樣,通過上面的測試,是否是覺的Span<T>確實是名不虛傳?的確,在上面幾個常見場景中,Span<T>的高性能確實與衆不同,差很少是10倍的性能優點!看到這裏,小夥伴們是否是覺的字符串操做全改爲Span<T>就好了?那下面的兩個測試會讓你們看清現實,在String.Contains中表現還不如原生的。指針
1、String.Contains 測試code
1 var t1 = StopWacherHelper.DoTimer(() => 2 { 3 for (int i = 0; i < count; i++) 4 { 5 str.Contains(subStr); 6 } 7 }); 8 9 Console.WriteLine($"string.Contains {count} 次用時:{t1} 毫秒");
1 var t2 = StopWacherHelper.DoTimer(() => 2 { 3 var strSpan = str.AsSpan(); 4 5 var subStrSpan = subStr.AsSpan(); 6 7 for (int i = 0; i < count; i++) 8 { 9 strSpan.Contains(subStrSpan, StringComparison.CurrentCulture); 10 } 11 }); 12 13 Console.WriteLine($"Span<T>.Contains {count} 次用時:{t2} 毫秒");
仔細一看,不對啊,Span<T>的Contains裏面有其它的大小寫和語言相關的判斷啊。好,那再換一個原生方法對比測試一下。blog
2、String.Compare 測試ip
1 var t1 = StopWacherHelper.DoTimer(() => 2 { 3 for (int i = 0; i < count; i++) 4 { 5 string.Compare(str, subStr, true); 6 } 7 }); 8 9 Console.WriteLine($"string.Compare {count} 次用時:{t1} 毫秒");
1 var t2 = StopWacherHelper.DoTimer(() => 2 { 3 var strSpan = str.AsSpan(); 4 5 var subStrSpan = subStr.AsSpan(); 6 7 for (int i = 0; i < count; i++) 8 { 9 strSpan.Contains(subStrSpan, StringComparison.CurrentCultureIgnoreCase); 10 } 11 }); 12 13 Console.WriteLine($"Span<T>.Contains {count} 次用時:{t2} 毫秒");
仍是被反殺了,這說明Span<T>的這個Contains方法可能真的只能在某些地方纔能用,否則性能反而會有所降低。字符串
若是對上述感興趣,能夠點擊這裏下載測試源碼,更多請點擊左下角的推薦,謝謝~