Better replacement for Artifact Indexes #106
Merged
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
loewenheim
reviewed
Jun 23, 2023
text/0106-artifact-indices.md
Outdated
| - **pro**: Solves file decompression performance of Symbolicator. | ||
| - **pro**: We _assume_ that most files inside of bundles are unused. | ||
| - **pro**: We _assume_ that a lot of files will not change across bundles (polyfills, dependencies, etc). | ||
| - **con**: We need a better way to store many small files. |
There was a problem hiding this comment.
Better in what way? Is it too expensive, too hard to organize, or something else?
There was a problem hiding this comment.
Lets see if @mitsuhiko wants to chime in here, as he was very vocal against doing this. I believe the reason is that depending on storage vendor, you are billed by number of files, which can get extremely expensive storing a ton of small files.
liamjones
reviewed
Jul 14, 2023
iambriccardo
force-pushed
the
swatinem/artifact-index
branch
from
da3fcb9
to
6dae095
Compare
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.
We want to come up with a way to support SourceMap processing or in particular access to files needed for SourceMap
processing that supports more customer use-cases, is correct, and is efficient to implement and scale.
Rendered RFC