flosell / flosell/trailscraper
Try optimizing select by not parsing into objects
Open
enhancement
performance
select-feature
- Dominant language
- Python
- Stars
- 838
- Forks
- 38
- Avg merge
- 2m
- Merged PRs (30d)
- 14
Description
In select, we only do a bit of filtering on top of CloudTrail records. But we parse them into an object structure first, then filter on that, then marshalling back into JSON. This could very likely be optimized.
Other optimization ideas:
* Can we stream print and read JSON instead of waiting for everything to be rendered, then everything to be parsed?
Contributor guide
Assessment
This issue has not been assessed yet.