Skip to content

fix: reboot threads on opcache reset and watcher#2364

Draft
AlliBalliBaba wants to merge 34 commits intomainfrom
fix/reboot-threads-on-opcache-reset-and-watcher
Draft

fix: reboot threads on opcache reset and watcher#2364
AlliBalliBaba wants to merge 34 commits intomainfrom
fix/reboot-threads-on-opcache-reset-and-watcher

Conversation

@AlliBalliBaba
Copy link
Copy Markdown
Contributor

Alternative to #2073 that reboots all threads instead

@AlliBalliBaba
Copy link
Copy Markdown
Contributor Author

This PR is based on the changes in #2073. Instead of calling opcache sirextly, we just reset the whole php runtime.

I haven't testes the additional overhead yet or the impact on file watching, but it might be a cleaner aolution, bypassing opcache race conditions entirely.

@AlliBalliBaba
Copy link
Copy Markdown
Contributor Author

When measuring with real-life projects, restart time slows down about 4x from ~12ms to ~48ms.

Maybe that's not significant, maybe it's too much. Would be nice to also measure the difference on Mac.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants