Skip to content

Fix typo#1

Merged
andimarek merged 1 commit intographql-java:masterfrom
hannesj:master
Jul 13, 2015
Merged

Fix typo#1
andimarek merged 1 commit intographql-java:masterfrom
hannesj:master

Conversation

@hannesj
Copy link
Contributor

@hannesj hannesj commented Jul 13, 2015

No description provided.

andimarek pushed a commit that referenced this pull request Jul 13, 2015
@andimarek andimarek merged commit 7616045 into graphql-java:master Jul 13, 2015
@andimarek
Copy link
Member

Thanks!

andimarek added a commit that referenced this pull request Jul 16, 2015
dminkovsky pushed a commit that referenced this pull request Dec 18, 2016
Added 'query' and 'mutation' as keywords in the grammar
bbakerman pushed a commit that referenced this pull request May 18, 2017
liqweed added a commit to liqweed/graphql-java that referenced this pull request Jan 5, 2020
Copilot AI added a commit that referenced this pull request Feb 19, 2026
Detailed investigation of options to reduce the #1 allocation hotspot (10.21%, 7.9GB).

Analyzed 6 optimization strategies:
1. Object Pooling (8-10% impact, high risk) - Not recommended
2. Reduce Object Size (2-3% impact, low risk) - Promising
3. Flyweight Pattern (3-5% impact, medium risk) - Recommended
4. Lazy Builder (1-2% impact, very low risk) - Quick win
5. Copy-on-Write (2-3% impact, high complexity) - Not recommended
6. Value Objects/Records (5-8% future impact) - Future consideration

Recommended phased implementation:
- Phase 1: Quick wins (1-2%) - Audit transform usage, add specialized methods
- Phase 2: Structural (3-5%) - Flyweight pattern, consolidate rare fields
- Phase 3: Advanced (5-8%) - Object pooling if needed

Each option includes code examples, pros/cons, risk assessment, and validation approach. Conservative estimate: 3-5% throughput improvement.

Co-authored-by: andimarek <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants