Run results for: memo vs no-memo vs incorrect- memo

Run details:

User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.66 Safari/537.36

Browser: Chrome 87

Operating system: Windows

Device Platform: Desktop

Date tested: 3 years ago

Test name	Executions per second
NoMemo - string child	15736.6 Ops/sec
Memo - string child	19318.8 Ops/sec
Memo - instance child	14763.2 Ops/sec
NoMemo - instance child	15239.5 Ops/sec

HTML Preparation code:

<div id="root"></div>

<script src="https://unpkg.com/react@16/umd/react.development.js"></script>
<script src="https://unpkg.com/react-dom@16/umd/react-dom.development.js"></script>

Script Preparation code:



var NoMemo = function({children}) {
  return React.createElement("div", { children: children });
}

var Memo = React.memo(NoMemo)

var StringChild = function () {return 'children'}

var DivChild = function () {
  return React.createElement('div', {}, 'children', ' in ', ' div');
}
var root = document.getElementById('root');

Tests:

NoMemo - string child
ReactDOM.render(React.createElement(NoMemo, {}, StringChild()), root);
Memo - string child
ReactDOM.render(React.createElement(Memo, {}, StringChild()), root);
Memo - instance child
ReactDOM.render(React.createElement(Memo, {}, DivChild()), root);
NoMemo - instance child
ReactDOM.render(React.createElement(NoMemo, {}, DivChild()), root);

Run results for: memo vs no-memo vs incorrect- memo

NoMemo - string child

Memo - string child

Memo - instance child

NoMemo - instance child