With the merge of other recent performance improvement PRs I'm actually not seeing any meaningful performance benefit from this PR anymore. Can you re-run your tests with latest code in 11.x? Mark as ready for review if you want me to take another look or after you comment.

@taylorotwell

This PR is not needed anymore.

UPDATE:
I'm not sure how, but this PR without View::composer doesn't have any effect and if we use this PR with View::composer still there is performance improvement.

Before:

After:

My closed PR (#51141) also can improve performance.

Without in-memory cache support for Blade:

With in-memory cache support for Blade:

Note: The first and second test runs with different codes for testing.

@taylorotwell
This PR can cause side effect issues as it caches view data.

web.php:

Route::get('/', function () {
    return view('home');
});

home.blade.php:

<x-sample param1="Hello" />
<hr />
<x-sample param1="Hello" param2="World" />
<hr />
<x-sample param1="Hello" />

sample.blade.php:

@if (isset($param1))
    <p>Param 1: {{ $param1 }}</p>
@else
    <p>Param 1 is not set</p>
@endif

@if (isset($param2))
    <p>Param 2: {{ $param2 }}</p>
@else
    <p>Param 2 is not set</p>
@endif

Output:

Fixed the reuse data issue and this PR still can improve performance while using View::compose.

Without view instance caching:

With view instance caching:

Causing other side effects, closing the PR.