Undo/Redo is called "abusively" and has very bad impact on performances of JMeter

[asfimport]

@pmouawad (Bug 57043):
As per Ubik Load Pack support report :

• Undo/Redo is called "abusively" when for example you:

1. Search for a node by name
2. In Module Controller GUI, when you expand a node

Version: Nightly
Severity: normal
OS: All

Duplicates:

• Undo/Redo function causes freeze and high memory usage when searching a large .jmx file #3724
• Find (CTRL-f) is extremely slow even with small tests #3732

Duplicated by:

• Inconsistency with the undo/redo log #3442

Blocks:

• Undo-redo support on Test Plan tree modification #1930

[asfimport]

@pmouawad (migrated from Bugzilla):
Hello,
I notice big slowdowns of JMeter with nightly build related to Undo/Redo feature.
Scenario:

• I load a Test Plan with something like 218 elements (1.5m)
• I takes around 23 seconds to load with nightly vs 1.5 seconds on 2.11 on a MacBook Pro 2.7 Ghz Intel Core i7 16 Gb and -Xms2g -Xmx3g

Analyzing this, it is related to the fact that UndoHistory#add is called for every addition of a node (> 218 times) , an entry is added in history and finally undoHistory is cleaned up.

With default settings (I disabled by default undo, I get same load time as 2.10).

We need to improve the undo algorithm.
Regards

[asfimport]

@pmouawad (migrated from Bugzilla):
Affects Nightly (before 2.12) of 2th October 2014

[asfimport]

@pmouawad (migrated from Bugzilla):
This has been improved by Emilian Bold work within #3442

This bug has been marked as a duplicate of #3442