This repository has been archived by the owner on Jul 19, 2023. It is now read-only.
Experimenting with storing stacktraces differently #757
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.
With our given problems around retrieving esp. stacktraces in a reasonable amount of time. I have been experimenting a bit.
Two ideas:
I will report back if any of the provide more tangible results.
This is the current size comparision between status quo and the self referencing model: