Suspense Boundary inside `layout.tsx` with `ppr` and `dynamicIO` enabled

[rich oyster]

Hi guys, I was watching theo's video on why is next.js so slow and my mental model for DynamicIO + PPR went downhill after the part he adds a Suspense Boudary wrapping the children in the layout file and that doesn't work.
I've tried to follow the explanation but I didn't really get it why it didn't work...
I thought the compiler would pre-render everything until the first async component for that route (including layouts) and put that in the static bundle for the route.
Can anyone please explain what I'm missing here?

[foggy quest]

Post created!

🔎 This post has been indexed in our web forum and will be seen by search engines so other users can find it outside Discord

🕵️ Your user profile is private by default and won't be visible to users outside Discord, if you want to be visible in the web forum you can add the "Public Profile" role in id:customize

✅ You can mark a message as the answer for your post with Right click -> Apps -> Mark Solution
(if you don't see the option, try refreshing Discord with Ctrl + R)

[kindred geyser]

the way I understood it was that when you go to a specific route it loads the page.tsx file, but it doesn't reload the layout.tsx .. because the suspense boundary is in the layout.tsx file it doesn't load the suspense boundary when changing pages/routes