Skip to content

Conversation

@skurfuerst
Copy link
Member

@skurfuerst skurfuerst commented May 16, 2023

neos part: neos/neos-development-collection#4286

... this ensures that during publishing of nodes, we do not fork sub-processes for event processing (for every event). This speeds up the system usually by at least factor 2-3 during these operations.

It could have some side-effects if caches were not properly cleared, but at least I did not see any yet (and we run tests often with this flag).

Resolves: neos/neos-development-collection#4285

... this ensures that during publishing of nodes, we do not fork
sub-processes for event processing (for every event). This speeds
up the system usually by at least factor 2-3 during these operations.

It *could* have some side-effects if caches were not properly cleared,
but at least I did not see any yet (and we run tests often with this flag).

Resolves: neos/neos-development-collection#4285
Copy link
Member

@mhsdesign mhsdesign left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ill mark this as blocked until our discussion in neos is resolved: neos/neos-development-collection#4286 (review)

@mhsdesign mhsdesign marked this pull request as draft February 21, 2025 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

9.0 Discussion Feature Label to mark the change as feature

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Improve performance for publish/discard of workspaces by using the synchronous mode

3 participants