blocks|key|770679|text|不，这只是以两种不同的方式表达的相同的操作。在那里什么也得不到。如果你想得到一般性的提示，我建议你仔细研究一下there's+a+good+book+available。如果您必须优化特定的程序，请使用跟踪工具(足够新的版本中的transaction+SAT+)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|770680|entityMap|0|LINK|mutability|MUTABLE|url|https://www.sap-press.com/abap-performance-tuning_2092/^0|3I|3|1J|T|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]]|D|@$9|Q|A|R|1|S]]|E|$]]|$1|F|3|-4|5|6|7|T|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

No, that is just the same operation expressed in two different ways. Nothing to gain there. If you're out for generic hints, <a href="https://www.sap-press.com/abap-performance-tuning_2092/" rel="nofollow">there's a good book available</a> that I'd recommend studying in detail. If you have to optimize a specific program, use the tracing tools (transaction <code>SAT</code> in sufficiently current releases).

blocks|key|150287|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|150288|“要将数据对象源的值赋给变量目标，请使用以下语句：|150289|MOVE+source+TO+destination.|code-block|syntax|javascript|150290|或等效的语句|150291|destination+=+source.|150292|“|150293|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|P|7|@]|8|@]|9|$]]|$1|A|3|B|4|5|6|Q|7|@]|8|@]|9|$]]|$1|C|3|D|4|E|6|R|7|@]|8|@]|9|$F|G]]|$1|H|3|I|4|5|6|S|7|@]|8|@]|9|$]]|$1|J|3|K|4|E|6|T|7|@]|8|@]|9|$F|G]]|$1|L|3|M|4|5|6|U|7|@]|8|@]|9|$]]|$1|N|3|-4|4|5|6|V|7|@]|8|@]|9|$]]]|O|$]]

The two statements are <a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/fc/eb3260358411d1829f0000e829fbfe/content.htm" rel="nofollow">equivalent</a>:

"
To assign the value of a data object source to a variable destination, use the following statement:

<pre><code>MOVE source TO destination.
</code></pre>

or the equivalent statement

<pre><code>destination = source.
</code></pre>

"

blocks|key|770770|text|不，它们是一样的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|770771|这是我多年的性能提升中的几个快速提示：|770772|1)如果您在可能的情况下使用移动对应，您的代码可以更加简洁、模块化和可扩展(在很久以前，这是不受欢迎的，但这样做的技术原因通常不再适用)。|770773|2)随时使用SAT，并确保开启内部表跟踪。这就像是打开灯，而不是在黑暗中被家具绊倒。|770774|3)让数据库层为你做尽可能多的工作。尽可能地尝试组合查询，尤其是在组合结果集时。由一个连接链接的两个查询通常比select+>+itab+>+select+FOR+ALL+ENTRIES好得多。|770775|4)这有点高级，但对于所有条目，其性能通常比短语中等效的select-options慢得多。这似乎是因为后者被构建为对数据库层的一个大查询，而前者需要多次访问数据库层。当然，需要注意的是，如果select选项中有太多记录，则在数据库层生成的查询将超过系统允许的大小，但在此限制内可能会获得较大的性能提升。一般来说，SAP就是喜欢选择选项。|770776|5)索引，索引，索引！|770777|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

No, they're the same.

Here's a couple quick hints from my years of performance enhancement: 

1) if you use move-corresponding where possible, your code can be a lot more concise, modular, and extendable (in the distant past this was frowned upon but the technical reasons for this are generally not applicable anymore).

2) Use SAT at every opportunity, and be sure to turn on internal table tracking. This is like turning on the lights versus stumbling over furniture in the dark.

3) Make the database layer do as much work as possible for you. Try to combine queries wherever possible, especially when combining result sets. Two queries linked by a join is usually much better than select > itab > select FOR ALL ENTRIES.

4) This is a bit advanced, but FOR ALL ENTRIES often has much slower performance than the equivalent select-options IN phrase. This seems to be because the latter is built as one big query to the database layer while the former requires multiple trips to the database layer. The caveat, of course, is that if you have too many records in your select-options the generated query at the database layer will exceed the allowable size on your system, but large performance gains are possible within that limitation. In general, SAP just loves select-options.

5) Index, index, index!

blocks|key|149717|text|首先，移动并不会对性能产生多大影响。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|149718|对我工作过的项目有很大影响的是：|149719|149720|嵌套循环(非常邪恶)。例如，遍历所有文档，并为每个文档选择single以检查它，允许显示公司代码。相反，应该列出公司代码，从db中查询一次，并参考此结果表。|ordered-list-item|149721|在可能的情况下使用哈希表或排序表。在不可能的情况下，使用标准表，但按键对其排序，并使用"binary+search".|149722|Select+from+DB+by+all+key+field“。如果不可能，请考虑创建索引。对于小而简单的selects，使用joins。对于较大的selects，使用joins仍然会更快，但很难跟进。|149723|的小问题-使用字段符号读取表行，这会使速度更快。|149724|149725|entityMap^0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|S|8|@]|9|@]|A|$]]|$1|E|3|F|5|G|7|T|8|@]|9|@]|A|$]]|$1|H|3|I|5|G|7|U|8|@]|9|@]|A|$]]|$1|J|3|K|5|G|7|V|8|@]|9|@]|A|$]]|$1|L|3|M|5|G|7|W|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|P|$]]

First of all move does not really affect much performance.

What is affecting quite a lot in the projects I worked for is following:

<ol>
<li>Nested loops (very evil). For example, loop through all documents, and for each document select single to check it company code is allowed to be displayed.
Instead, make a list of company codes, consult them all once from db and consult this results table instead.</li>
<li>Use hash or sorted tables where possible. Where not possible, use standard table, but sort it by keys and use "binary search".</li>
<li>Select from DB by all key fields. If not possible, consider creating indexes.
For small and simple selects, use joins. For bigger selects using joins will still work faster, but would be difficult to follow up.</li>
<li>Minor thing - use field symbols to read table line, this makes it much faster.</li>
</ol>

blocks|key|150311|text|1)在ABAP语言中使用SELECT语句时要小心。不必要的数据库连接大大降低了程序的性能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|150312|2)在函数中使用内部表时，请参照调用，以减少内存占用。|150313|按引用调用:传递指向内存的指针location.Changes对子例程内的变量进行操作会影响子例程外部的变量。|150314|3)不应将内部表与工作区一起使用。|150315|4)在使用嵌套循环时，使用排序算法。|offset|length|style|BOLD|150316|entityMap^0|0|0|0|0|5|4|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|S|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|T|8|@$J|U|K|V|L|M]]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

1) You should be careful while using SELECT statement in ABAP language.
Unnecessary database connections significantly decreases the performance of ABAP program.

2) While using internal table with functions you should call it by reference to reduce memory usage.

Call By Reference:
Passes a pointer to the memory location.Changes made to the
variable within the subroutine affects the variable outside
the subroutine.

3)Should not use internal tables with workarea.

4)While using nested loops, use sorting algorithms.

blocks|key|4602810|text|它们是相同的，就像ADD关键字和%2B操作符一样。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4602811|如果你确实想优化你的ABAP，我发现最大的罪魁祸首是：|4602812|4602813|未正确使用二进制查找和/或(内部)表键。当涉及到表的使用时，ABAP的语法是完全不能理解的。知道如何有效地使用表格。基本上写出更好/最优/优雅的高级代码。这永远是赢家！|unordered-list-item|4602814|更少的指令和更少的时间。命中的指令越少，程序的运行速度就越快。这在紧凑的循环中很重要。我知道这听起来很明显，但是ABAP太慢了，如果你真的想优化关键程序，这将会有所不同。(我们有运行数天的进程...刮掉一个小时左右的头发会让difference!)|4602815|Don't混杂在一起。一些隐式转换有一点开销...例如，如果您正在初始化string数据类型，则使用带(反号)引号的正确文字字符串：literal。这也适用于使用键在表中查找...使用完全匹配的datatypes.|4602816|Function调用...我再怎么强调函数调用的开销也不为过。你拥有的越少越好。违背了真正的计算机程序员的想法，但你已经知道了……ABAP是一个特例。|4602817|循环使用ASSIGNING+(或REF+TO+-在某些类型上略慢)，避免像瘟疫一样进入。|4602818|4602819|PS:还要记住，SWITCH语句只是美化了的IF条件语句……因此，将最常见的条件移到顶部！|4602820|entityMap^0|9|3|G|1|0|0|0|0|0|10|6|1U|7|0|0|4|9|G|6|0|0|8|6|M|2|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]|$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|13|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|14|8|@]|D|@]|E|$]]|$1|I|3|J|5|K|7|15|8|@]|D|@]|E|$]]|$1|L|3|M|5|K|7|16|8|@]|D|@]|E|$]]|$1|N|3|O|5|K|7|17|8|@$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|P|3|Q|5|K|7|1C|8|@]|D|@]|E|$]]|$1|R|3|S|5|K|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|T|3|-4|5|6|7|1I|8|@]|D|@]|E|$]]|$1|U|3|V|5|6|7|1J|8|@$9|1K|A|1L|B|C]|$9|1M|A|1N|B|C]]|D|@]|E|$]]|$1|W|3|-4|5|6|7|1O|8|@]|D|@]|E|$]]]|X|$]]

They are the same, as is the <code>ADD</code> keyword and <code>+</code> operator.

If you do want to optimize your ABAP, I have found the largest culprits to be:

<ul>
<li>Not using binary lookups and/or (internal) table keys properly.
The syntax of ABAP is brain-dead when it comes to table use. Know how
to work with tables efficiently. Basically write
better/optimal/elegant high-level code. This is always a winner!</li>
<li>Fewer instructions == less time. The fewer instructions you hit the
faster the program will run. This is important in tight loops... I
know this sounds obvious, but ABAP is so slow, that if you are really
trying to optimize critical programs, this will make a difference.
(We have processes that run days... and shaving off an hour or so
makes a difference!)</li>
<li>Don't mix types. There is a little bit of overhead to some
implicit conversions... for instance if you are initializing a
<code>string</code> data type, then use the correct literal string with
(backtick) quotes: `literal`. This also counts for looking up in
tables using keys... use exact match datatypes.</li>
<li>Function calls... I cannot stress the overhead of function calls
enough... the less you have the better. Goes against anything a real
computer programmer believes, but there you have it... ABAP is a
special case.</li>
<li>Loop using <code>ASSIGNING</code> (or <code>REF TO</code> - slightly slower on certain
types), avoid INTO like a plague.</li>
</ul>

PS: Also keep in mind that <code>SWITCH</code> statements are just glorified <code>IF</code> conditionals... thus move the most common conditions to the top!

blocks|key|770829|text|您可以使用ADT+Eclipse创建CDS。或者视图(Se11)具有良好的选择性能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|770830|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can create CDS with ADT Eclipse. Or views(se11) have good performance for selecting.

blocks|key|4120758|text|“将a移动到”b和"a+=+b“在ABAP中是相同的。没有性能差异，"MOVE“只是一个更明显、更引人注目的版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4120759|但如果你谈到“移动对应”，是的，这是性能上的差异。它对代码更实用，但实际上运行速度比直接移动要慢。|4120760|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|$]]

"MOVE a TO" b and "a = b" are just same in ABAP. There is no performance difference "MOVE" is just a more visible, noticeable version.

But if you talk about "MOVE-CORRESPONDING", yes, there is a performance difference. It's more practical to code, but actually runs slower then direct movement.

Is there any kind of performance gain between 'MOVE TO' vs x = y? I have a really old program I am optimizing and would like to know if it's worth it to pull out all the MOVE TO. Any other general tips on ABAP optimization would be great as well.

Performance difference between MOVE and = assignment in ABAP

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

'MOVE TO‘和x= y之间有没有什么性能上的提升？我有一个非常老的程序，我正在优化，我想知道它是否值得把所有的移动。任何其他关于ABAP优化的一般技巧也会很棒。

问ABAP中MOVE和=赋值的性能差异
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ABAP中MOVE和=赋值的性能差异EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问ABAP中MOVE和=赋值的性能差异
EN