执行一个SQL查询时，太多是394的持续时间？ [英] Is a duration of 394 when executing a SQL query too much?

问题描述

我有这个连接池的问题：

I had this connection pool problem:

<一个href=\"http://stackoverflow.com/questions/670774/how-to-solve-a-connection-pool-problem-between-asp-net-and-sql-server\">How解决ASP.NET和SQL Server之间的连接池问题？

和我现在使用的跟踪SQL事件探查器，我发现一些查询约需400时间完成并返回数据。

And I am now tracing using the SQL profiler, and I found some queries take about 400 duration to finish and return data.

是价值太多了？

难道导致previous连接池的问题？

Could it cause the previous connection pool problem?

推荐答案

400指400毫秒，或0.4秒。

400 means 400 ms, or 0.4 seconds.

无论太长实际上取决于。如果这是你的头版或其他高流量区域，那么这是太多，除非这是一个内部网站。您可能需要重新考虑如何能够获得这些数据，或者使用缓存来减少次数实际上必须运行查询。

Whether that is too long really depends. If this is your front page or other high traffic area, then that's too much unless this is an intranet site. You may need to rethink how that data can be obtained, or use caching to reduce the number of times you actually have to run the query.

如果这是一份报告，或其他更复杂的页面，然后400毫秒不脱节。在最好的情况，你可能要检查如果查询可以做得快一点，以改善整体用户体验。

If this is a report, or other more involved page, then 400 ms is not out of line. At best you might want to check if the query can be done a bit faster to improve the overall user experience.

您可能还需要运行优化顾问，以确定是否查询只运行缓慢的，因为你没有正确的索引。

You may also want to run the Tuning Advisor to determine if the queries are only running slow because you don't have the correct indexes.

这篇关于执行一个SQL查询时，太多是394的持续时间？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！