Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[don't merge] Check compilation server without hxb #11529

Closed
wants to merge 5 commits into from

Conversation

Simn
Copy link
Member

@Simn Simn commented Jan 31, 2024

I'm opening this just so I don't forget about the branch. All this does is disable the hxb-cache to test if the memory-cache still works. I want to make sure that we keep this branch updated do that we don't run into any surprises.

@kLabz
Copy link
Contributor

kLabz commented May 15, 2024

Should we allow this through a define (possibly a "hidden" one) in 5.0 (including previews) for projects where in memory cache was never a problem?

For such projects (haxe-formatter for example) hxb overhead can very annoying, with the situation where almost no modules gets invalidated being common and timing goes from 20~40ms to 100ms (latest hxb optimizations means hxb cache is usually slightly faster even on those projects when we start to invalidate modules, but for projects using diagnostics we go back to previously mentioned cases very often).

@Simn
Copy link
Member Author

Simn commented May 15, 2024

Makes sense to me, and we should also run at least the server tests like that.

@kLabz
Copy link
Contributor

kLabz commented May 15, 2024

Not needed anymore since #11668 got merged

@kLabz kLabz closed this May 15, 2024
@kLabz kLabz deleted the check_memory_cache branch May 28, 2024 09:33
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