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

Improve the new GC #59

Open
1 of 6 tasks
playXE opened this issue Jun 30, 2021 · 1 comment
Open
1 of 6 tasks

Improve the new GC #59

playXE opened this issue Jun 30, 2021 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@playXE
Copy link
Collaborator

playXE commented Jun 30, 2021

The new GC already performs very nicely but some improvements can be done:

  • Lazy-sweeping
  • Concurrent marking
  • Bitmap marking. Required for concurrent marking, this means we have to continuously have two bitmaps one for seeing what objects are allocated and the second one for mark bits, and each large allocation needs an additional mark field.
  • WebKit's like Subspaces.
    With subspaces, we can have collectible and uncollectible one. For example all JS strings might be allocated in vm.heap.string_subspace and regular objects in vm.heap.object_subspace. There are a few problems though: should each subspace mmap a large chunk of memory for allocating blocks or there should be one large chunk of memory per runtime instance?
  • Internal pointers
  • Write barriers
@playXE playXE added the enhancement New feature or request label Jun 30, 2021
@playXE playXE self-assigned this Jul 2, 2021
@playXE
Copy link
Collaborator Author

playXE commented Jul 2, 2021

Bitmap marking is implemented but three-color abstraction is still there for incremental or concurrent marking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant