XslCompiledTransform 的 XML 大小限制
.NET (3.5) 中的 XslCompiledTransform 应用 XSLT 的 XML 大小是否有任何限制？另外，传递给 XSLT 的参数长度是否有限制？
更新： 我指的不是参数的数量，而是作为参数传递的字符串的长度以及应用 XSLT 的 XML 文本的长度。
Is there any limit for XML size for which XSLT is applied by XslCompiledTransform in .NET (3.5)? Also, is there any limitation for a length of parameters passed to XSLT?
UPDATE: I did not mean the amount of parameters, but the length of a string, which is passed as a parameter and length of an XML text, to which XSLT is applied.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
不。
内存消耗通常被 XML 文档的大小所淹没。我听说过的一个有点规则的规则是，将 XML 文档的大小乘以 5，这样您就可以得到在 RAM 中保存该文档可能需要的 RAM 的大致大小。
因此，2GB XML 文档很有可能在 12GB RAM 64 位机器上进行处理。
请注意，无法保证此类处理可能需要多长时间 - 只是可以将此类文档保存在内存中。
No.
The memory consumption is usually overwhelmed by the size of the XML document. A somewhat course rule I have heard of is to multiply the size of the XML document by 5 and this would give you the approximate amount of RAM that might be necessary to hold that document in RAM.
So, a 2GB XML document has good chances of being processed on a 12GB RAM 64-bit machine.
Note, that there is no guarantee how long such processing may take -- just that it would be possible to hold such a document in memory.
据我所知，对于 XslCompiledTransform 类。
但是，应用 XSL 转换可能会显着增加应用程序的内存消耗，具体取决于正在处理的 XML 数据量。
在某些情况下，它甚至可能超出 32 位进程的 2 GB 限制。如果发生这种情况，应用程序可能必须以 64 位编译和运行。
As far as I know there aren't any hard limits on the amount of XML or the length of string parameters that can be processed by the XslCompiledTransform class.
However, applying an XSL transformation might potentially increase the memory consumption of your application considerably, depending on the amount of XML data being processed.
In some cases it may even go beyond the 2 GB limit imposed to 32-bit processes. If this situation should occur, the application might have to be compiled and run in 64-bit.