Limit of total number of generated (de)serializer
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 87
- Forks
- 73
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 1
Description
Currently, there is no limit of the total number of de/serializer classes fast-avro could generate and load during runtime. So, the generated code may saturate the application code cache if there are too many schemas, and it might cause GC issues.
We can set a hard-limit or leverage a LRU cache to limit the maximum number of de/serializer classes that can be loaded during runtime.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating fast-avro's runtime path for generating and loading de/serializer classes, then assess how many schema-specific classes can accumulate. Decide whether the completed behavior should use a hard limit or an LRU cache, and verify that excessive schemas no longer allow unbounded class loading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100