我有一個(gè)使用Entity Framework 6處理數(shù)據(jù)庫(kù)的MVC站點(diǎn)，并且我一直在嘗試對(duì)其進(jìn)行更改，以使所有內(nèi)容都作為異步控制器運(yùn)行，并且對(duì)數(shù)據(jù)庫(kù)的調(diào)用作為它們的異步對(duì)應(yīng)對(duì)象（例如ToListAsync（）而不是ToList（））我遇到的問(wèn)題是，僅將查詢(xún)更改為異步已使它們的運(yùn)行速度變得異常慢。下面的代碼從我的數(shù)據(jù)上下文中獲取“相冊(cè)”對(duì)象的集合，并將其轉(zhuǎn)換為相當(dāng)簡(jiǎn)單的數(shù)據(jù)庫(kù)聯(lián)接：// Get the albumsvar albums = await this.context.Albums    .Where(x => x.Artist.ID == artist.ID)    .ToListAsync();這是創(chuàng)建的SQL：exec sp_executesql N'SELECT [Extent1].[ID] AS [ID], [Extent1].[URL] AS [URL], [Extent1].[ASIN] AS [ASIN], [Extent1].[Title] AS [Title], [Extent1].[ReleaseDate] AS [ReleaseDate], [Extent1].[AccurateDay] AS [AccurateDay], [Extent1].[AccurateMonth] AS [AccurateMonth], [Extent1].[Type] AS [Type], [Extent1].[Tracks] AS [Tracks], [Extent1].[MainCredits] AS [MainCredits], [Extent1].[SupportingCredits] AS [SupportingCredits], [Extent1].[Description] AS [Description], [Extent1].[Image] AS [Image], [Extent1].[HasImage] AS [HasImage], [Extent1].[Created] AS [Created], [Extent1].[Artist_ID] AS [Artist_ID]FROM [dbo].[Albums] AS [Extent1]WHERE [Extent1].[Artist_ID] = @p__linq__0',N'@p__linq__0 int',@p__linq__0=134實(shí)際上，這不是一個(gè)非常復(fù)雜的查詢(xún)，但是SQL Server運(yùn)行它幾乎需要6秒鐘。SQL Server Profiler報(bào)告它需要5742毫秒才能完成。如果我將代碼更改為：// Get the albumsvar albums = this.context.Albums    .Where(x => x.Artist.ID == artist.ID)    .ToList();然后生成了完全相同的SQL，但是根據(jù)SQL Server Profiler，它只需要474毫秒即可運(yùn)行。該數(shù)據(jù)庫(kù)在“相冊(cè)”表中大約有3500行，實(shí)際上不是很多，并且在“ Artist_ID”列上有一個(gè)索引，因此應(yīng)該非?？?。我知道異步有開(kāi)銷(xiāo)，但是讓事情慢十倍對(duì)我來(lái)說(shuō)似乎有點(diǎn)陡峭！我在哪里錯(cuò)了？