-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Dockerfile: fixes #1159
Merged
Merged
Dockerfile: fixes #1159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: jsign <jsign.uy@gmail.com>
Signed-off-by: jsign <jsign.uy@gmail.com>
Signed-off-by: jsign <jsign.uy@gmail.com>
whyrusleeping
approved these changes
Jan 28, 2020
masih
added a commit
that referenced
this pull request
Mar 14, 2024
Changes the chain event indexing mechanism to index events solely by their emitter actor ID, instead of their address. This change means: 1) index can accommodate non-EVM actors, and 2) improved performance and efficiency due to reduced number of resolutions and storage footprint. The work introduces a caching mechanism to momentarily cache the resolutions to/fro actor ID and address. Further experimentation is needed to tune the cache for optimal performance. For now, the introduction of a unified cache reduces lookup time and memory allocation foot print compared to the previous implementation where ephemeral caches were being instantiated per event filter. Fixes #1159
masih
added a commit
that referenced
this pull request
Mar 15, 2024
Changes the chain event indexing mechanism to index events solely by their emitter actor ID, instead of their address. This change means: 1) index can accommodate non-EVM actors, and 2) improved performance and efficiency due to reduced number of resolutions and storage footprint. The work introduces a caching mechanism to momentarily cache the resolutions to/fro actor ID and address. Further experimentation is needed to tune the cache for optimal performance. For now, the introduction of a unified cache reduces lookup time and memory allocation foot print compared to the previous implementation where ephemeral caches were being instantiated per event filter. Fixes #1159
masih
added a commit
that referenced
this pull request
Mar 15, 2024
Changes the chain event indexing mechanism to index events solely by their emitter actor ID, instead of their address. This change means: 1) index can accommodate non-EVM actors, and 2) improved performance and efficiency due to reduced number of resolutions and storage footprint. The work introduces a caching mechanism to momentarily cache the resolutions to/fro actor ID and address. Further experimentation is needed to tune the cache for optimal performance. For now, the introduction of a unified cache reduces lookup time and memory allocation foot print compared to the previous implementation where ephemeral caches were being instantiated per event filter. Fixes #1159
masih
added a commit
that referenced
this pull request
Mar 16, 2024
Changes the chain event indexing mechanism to index events solely by their emitter actor ID, instead of their address. This change means: 1) index can accommodate non-EVM actors, and 2) improved performance and efficiency due to reduced number of resolutions and storage footprint. The work introduces a caching mechanism to momentarily cache the resolutions to/fro actor ID and address. Further experimentation is needed to tune the cache for optimal performance. For now, the introduction of a unified cache reduces lookup time and memory allocation foot print compared to the previous implementation where ephemeral caches were being instantiated per event filter. Fixes #1159
masih
added a commit
that referenced
this pull request
Apr 4, 2024
Changes the chain event indexing mechanism to index events solely by their emitter actor ID, instead of their address. This change means: 1) index can accommodate non-EVM actors, and 2) improved performance and efficiency due to reduced number of resolutions and storage footprint. The work introduces a caching mechanism to momentarily cache the resolutions to/fro actor ID and address. Further experimentation is needed to tune the cache for optimal performance. For now, the introduction of a unified cache reduces lookup time and memory allocation foot print compared to the previous implementation where ephemeral caches were being instantiated per event filter. Fixes #1159
masih
added a commit
that referenced
this pull request
Apr 4, 2024
Changes the chain event indexing mechanism to index events solely by their emitter actor ID, instead of their address. This change means: 1) index can accommodate non-EVM actors, and 2) improved performance and efficiency due to reduced number of resolutions and storage footprint. The work introduces a caching mechanism to momentarily cache the resolutions to/fro actor ID and address. Further experimentation is needed to tune the cache for optimal performance. For now, the introduction of a unified cache reduces lookup time and memory allocation foot print compared to the previous implementation where ephemeral caches were being instantiated per event filter. Fixes #1159
masih
added a commit
that referenced
this pull request
Apr 24, 2024
Changes the chain event indexing mechanism to index events solely by their emitter actor ID, instead of their address. This change means: 1) index can accommodate non-EVM actors, and 2) improved performance and efficiency due to reduced number of resolutions and storage footprint. The work introduces a caching mechanism to momentarily cache the resolutions to/fro actor ID and address. Further experimentation is needed to tune the cache for optimal performance. For now, the introduction of a unified cache reduces lookup time and memory allocation foot print compared to the previous implementation where ephemeral caches were being instantiated per event filter. Fixes #1159
masih
added a commit
that referenced
this pull request
Apr 29, 2024
Changes the chain event indexing mechanism to index events solely by their emitter actor ID, instead of their address. This change means: 1) index can accommodate non-EVM actors, and 2) improved performance and efficiency due to reduced number of resolutions and storage footprint. The work introduces a caching mechanism to momentarily cache the resolutions to/fro actor ID and address. Further experimentation is needed to tune the cache for optimal performance. For now, the introduction of a unified cache reduces lookup time and memory allocation foot print compared to the previous implementation where ephemeral caches were being instantiated per event filter. Fixes #1159
rvagg
pushed a commit
that referenced
this pull request
Apr 30, 2024
Changes the chain event indexing mechanism to index events solely by their emitter actor ID, instead of their address. This change means: 1) index can accommodate non-EVM actors, and 2) improved performance and efficiency due to reduced number of resolutions and storage footprint. The work introduces a caching mechanism to momentarily cache the resolutions to/fro actor ID and address. Further experimentation is needed to tune the cache for optimal performance. For now, the introduction of a unified cache reduces lookup time and memory allocation foot print compared to the previous implementation where ephemeral caches were being instantiated per event filter. Fixes #1159
masih
added a commit
that referenced
this pull request
Apr 30, 2024
Changes the chain event indexing mechanism to index events solely by their emitter actor ID, instead of their address. This change means: 1) index can accommodate non-EVM actors, and 2) improved performance and efficiency due to reduced number of resolutions and storage footprint. The work introduces a caching mechanism to momentarily cache the resolutions to/fro actor ID and address. Further experimentation is needed to tune the cache for optimal performance. For now, the introduction of a unified cache reduces lookup time and memory allocation foot print compared to the previous implementation where ephemeral caches were being instantiated per event filter. Fixes #1159
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Despite the Dockerfile created a non-privileged user and mosty prepared all for it, it was missing some further configs to being able to leverage it.
This also meant that the
.lotus
folder wasn't mapped to the intended docker volume, but in/root
which isn't a volume thus loosing state/keys/etc if the container is removed.Somewhat mentioned here
cc @eshon since #1154 is open too.