GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | |
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | |
GeezerVison is showing github.com — Fix typo by hannesj · Pull Request #1 · graphql-java/graphql-java Conversation
Contributor
No description provided.
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page. All reactions
Member
All reactions
Sorry, something went wrong. Uh oh!
There was an error while loading. Please reload this page.
dminkovsky
pushed a commit
that referenced
this pull request
Added 'query' and 'mutation' as keywords in the grammar
bbakerman
pushed a commit
that referenced
this pull request
liqweed
added a commit
to liqweed/graphql-java
that referenced
this pull request
Copilot AI
added a commit
that referenced
this pull request
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]>
dondonz
added a commit
that referenced
this pull request
…ath by eliminating a redundant getFieldDef lookup per field, removing an unnecessary ArrayList copy in list completion, and bypassing Builder allocation for FieldCollectorParameters in object completion.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
ReviewersNo reviewsUh oh!
There was an error while loading. Please reload this page. AssigneesNo one assignedLabels
None yet
ProjectsMilestoneNo milestoneDevelopmentSuccessfully merging this pull request may close these issues. Uh oh!
There was an error while loading. Please reload this page. 2 participantsAdd 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. | |
| You are visitor 01402503 — GeezerVison does not store the pages you look up. Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required. |
