blocks|key|3317672|text|不，使用GridView不会带来性能优势。一般而言，由于项被写入到GridView中并生成额外的ViewState，因此HTML会略微降低性能。您从GridView获得的好处包括易于使用或创建的命令事件和参数、允许您跟踪大型结果集中的关键字段的DataKey“属性包”，以及许多其他功能。我要补充的是，我已经在非常简单的结果集返回上使用过GridViews，并且没有看到任何明显的性能问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3317673|如果您只是从表查询中执行一些输出，而不担心与结果本身的数据进行过多的交互，那么“滚动您自己的”将提供一个很好的解决方案。|3317674|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

No, there are no performance benefits with using a GridView. In general, the GridView is going to decrease a little bit of performance due to the fact that items are written into the ViewState,and additional HTML is generated. The benefits you DO get from the GridView include command events and arguments that can be easily consumed or created, a DataKey "property bag" that allows you to track critical fields in a large result set, as well as many other things. I will add this caveat that I've used GridViews on even very simple result set returns and have not seen any significant performance problems.

If you are simply doing some output from a table query, and not worrying about doing too much interaction with the data from the results itself, "rolling your own" would provide a great solution.

blocks|key|3317702|text|当然，这取决于你的实现。几乎可以肯定的是，您可以构建运行速度比股票网格视图更快的东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3317703|问题是，你是怎么知道的？.Net中字符串连接的默认系统本质上是非常慢的，因此很容易意外地构建比常用网格视图慢得多的东西。当然，您也可以对其进行测试，但开发时间的投入可能会超过服务器的性能收益。|3317704|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Well, of course it depends on your implementation. You could almost certainly build something that runs faster than the stock gridview. 

The problem is, how would you know? The default system for string concatenation in .Net is by it's nature very slow, so it would be easy to accidentally build something that is much slower than the stock gridview. You could of course test things out, but the development time investment is likely to outweigh an server performance gains.

blocks|key|3317765|text|我将提出另一个解决方案。如果你不需要GridView的任何功能，为什么不使用中继器呢？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3317766|中继器使其实现简单，但也允许您完全控制生成的源代码。而不存在字符串连接性能的问题。|3317767|我发现与GridViews相比，中继器的性能略有提高。|3317768|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I am going to propose an alternate solution. If you don't need any of the features of a GridView, why not use a repeater.

A repeater keeps it simple for implementation, but also allows you to have full control over the generated source. Without the issue of string concatentation preformance.

I've found marginal performance improvements with repeaters over GridViews.

blocks|key|912863|text|在使用GridView和使用StringBuilder生成超文本标记语言之间存在另一种可能性。我说的是使用ASP+Table类。我已经看到，当我所做的只是输出数据时，使用它们比使用标准GridView具有令人印象深刻的速度优势。作为额外的好处，我可以在输出中添加一个按钮(或linkbutton)，并将其与事件处理程序连接起来，在这方面仍然可以获得GridView的功能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|912864|你可以这样使用它：|912865|Dim+tab+As+New+Table
For+Each+row+In+DataTable.Rows
++Dim+tabRow+as+New+TableRow
++For+Each+col+In+row.Columns
++++dim+tabCol+as+New+TableColumn
++++tabCol+.Text+=+row(col)
++++tabRow.Controls.Add(tabCol+)
++Next
++tab.Rows.Add(tabRow)
Next+
Page.Controls.Add(tab)|code-block|syntax|javascript|912866|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

There's an additional possibility here that exists between using a GridView and using a StringBuilder to generate HTML. I'm talking about using the ASP Table class. I have seen impressive speed benefits on using them over a standard GridView when all I'm doing is spitting out data. As an added bonus, I can add a button (or linkbutton) to my output and wire it up with an event handler and still get the functionality of a GridView in that regard.

You'd use it thus:

<pre><code>Dim tab As New Table
For Each row In DataTable.Rows
 Dim tabRow as New TableRow
 For Each col In row.Columns
 dim tabCol as New TableColumn
 tabCol .Text = row(col)
 tabRow.Controls.Add(tabCol )
 Next
 tab.Rows.Add(tabRow)
Next 
Page.Controls.Add(tab)
</code></pre>

Are there any performance benefits to me not using the gridview in asp.net for simple tables querying from a stored procedure and instead writing the html in server code myself. I'm sure my code would certainly be more concise in output.

asp.net gridview vs writing innerhtml

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

不使用asp.net中的网格视图从存储过程中查询简单的表，而是自己编写服务器代码中的html，这对我有什么性能上的好处吗？我确信我的代码在输出中肯定会更简洁。

问asp.net gridview与编写innerhtml
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问asp.net gridview与编写innerhtmlEN