在.NET 4.6.2上,Kestrel / IIS非常慢

时间:2016-12-23 16:43:43

标签: asp.net-core asp.net-core-mvc kestrel-http-server .net-4.6.2

我有一个NET 4.6.2 MVC(前端),它通过Rest与API(后端)通信,突然之间我们的测试服务器变得非常慢。

服务器上的其他应用程序显示正常,并且在本地运行此应用程序时,它的速度非常快。

我已经在它的终点测试了API,响应时间<10ms(缓存),使用NLog,我得到了一些来自Kestrel的结果,它似乎是在传入的请求中停止。

查看日志,有一个明确的3秒钟请求进入,没有任何反应。

我在这里有很多想法 - 这可能是服务器问题吗?因为它在当地工作正常吗?

2016-12-23 16:34:53.5251|1|Microsoft.AspNetCore.Hosting.Internal.WebHost|INFO|Request starting HTTP/1.1 GET http://myApplication.myTestServer.com/Request/Create


2016-12-23 16:34:57.3845|1|Microsoft.AspNetCore.Routing.RouteConstraintMatcher|DEBUG|Route value 'Request' with key 'pageNumber' did not match the constraint 'Microsoft.AspNetCore.Routing.Constraints.IntRouteConstraint'.


2016-12-23 16:34:57.3845|1|Microsoft.AspNetCore.Routing.RouteBase|DEBUG|Request successfully matched the route with name 'default' and template '{controller=Home}/{action=Index}/{id?}'. 
2016-12-23 16:34:57.3845|2|Microsoft.AspNetCore.Mvc.Internal.ActionSelector|DEBUG|Action 'myApplication.Controllers.RequestController.Create (myApplication)' with id 'de2f360e-a000-4ff0-94ea-2cff3afb5af1' did not match the constraint 'Microsoft.AspNetCore.Mvc.Internal.HttpMethodActionConstraint' 
2016-12-23 16:34:57.3845|1|Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker|DEBUG|Executing action myApplication.Controllers.RequestController.Create (myApplication) 
2016-12-23 16:34:57.3845|1|Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker|INFO|Executing action method myApplication.Controllers.RequestController.Create (myApplication) with arguments ((null)) - ModelState is Valid 
2016-12-23 16:34:57.4001|2|Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker|DEBUG|Executed action method myApplication.Controllers.RequestController.Create (myApplication), returned result Microsoft.AspNetCore.Mvc.ViewResult. 
2016-12-23 16:34:57.4001|2|Microsoft.AspNetCore.Mvc.Razor.RazorViewEngine|DEBUG|View lookup cache hit for view 'Create' in controller 'Request'. 
2016-12-23 16:34:57.4001|2|Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.ViewResultExecutor|DEBUG|The view 'Create' was found. 
2016-12-23 16:34:57.4001|1|Microsoft.AspNetCore.Mvc.ViewFeatures.Internal.ViewResultExecutor|INFO|Executing ViewResult, running view at path /Views/Request/Create.cshtml. 
2016-12-23 16:34:57.4001|5|Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector|TRACE|Performing unprotect operation to key {0c8426b3-7550-4bd9-9f7a-039549bbdf89} with purposes ('C:\Octopus\Applications\UK - Test\myApplication\2016.12.23.163307', 'Microsoft.AspNetCore.Antiforgery.AntiforgeryToken.v1'). 
2016-12-23 16:34:57.4001|31|Microsoft.AspNetCore.DataProtection.KeyManagement.KeyRingBasedDataProtector|TRACE|Performing protect operation to key {0c8426b3-7550-4bd9-9f7a-039549bbdf89} with purposes ('C:\Octopus\Applications\UK - Test\myApplication\2016.12.23.163307', 'Microsoft.AspNetCore.Antiforgery.AntiforgeryToken.v1'). 
2016-12-23 16:34:57.4001|6|Microsoft.AspNetCore.Antiforgery.Internal.DefaultAntiforgery|DEBUG|An antiforgery cookie token was reused. 
2016-12-23 16:34:57.4157|2|Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker|INFO|Executed action myApplication.Controllers.RequestController.Create (myApplication) in 25.6799ms 
2016-12-23 16:34:57.4157|9|Microsoft.AspNetCore.Server.Kestrel|DEBUG|Connection id "0HL1BA65KRN93" completed keep alive response. 
2016-12-23 16:34:57.4157|2|Microsoft.AspNetCore.Hosting.Internal.WebHost|INFO|Request finished in 3891.2205ms 200 text/html; charset=utf-8 

0 个答案:

没有答案