Autoresearch: Execution engine optimization (large in-memory query) by dondonz · Pull Request #4348 · graphql-java/graphql-java · GitHub
Skip to content

Autoresearch: Execution engine optimization (large in-memory query)#4348

Draft
dondonz wants to merge 3 commits intomasterfrom
claude/autoresearch-execution-large
Draft

Autoresearch: Execution engine optimization (large in-memory query)#4348
dondonz wants to merge 3 commits intomasterfrom
claude/autoresearch-execution-large

Conversation

@dondonz
Copy link
Copy Markdown
Member

@dondonz dondonz commented Mar 22, 2026

This is a bit of fun to see what Autoresearch can do

Summary

  • Autoresearch setup for optimizing LargeInMemoryQueryPerformance.benchMarkSimpleQueriesThroughput
  • Targets the core execution engine: ExecutionStrategy, ResultNodesInfo, field resolution, result assembly
  • 10M scalar field benchmark — cleanly isolates execution overhead
  • Designed for overnight autonomous optimization runs (200 iterations)

Approach

  • Profile-guided optimization using async-profiler
  • Targeted local test subset (graphql.execution.*) for fast iteration
  • Lessons from ENF autoresearch baked into program.md

Test plan

  • Run autoresearch loop locally
  • Verify improvements with full test suite on EC2
  • Review and cherry-pick winning optimizations

🤖 Generated with Claude Code

…ptimization

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Mar 22, 2026

echo "--- Asking Claude to make an optimization ---"
CLAUDE_OUTPUT=$(claude \
--model sonnet \
--dangerously-skip-permissions \
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yolo again!

I gave it a try with Opus and it was fine too

dondonz and others added 2 commits March 22, 2026 17:35
Use --permission-mode plan with explicit --allowedTools whitelist instead
of bypassing all permissions. The agent can read files, edit source code,
and run gradle (for profiling), but cannot run tests, git commit, or
perform other destructive operations. The outer harness handles those.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@dondonz
Copy link
Copy Markdown
Member Author

dondonz commented Apr 3, 2026

Trying a similar concept with https://github.com/kunchenguid/gnhf (Autoresearch meets Ralph loop)

@dondonz
Copy link
Copy Markdown
Member Author

dondonz commented Apr 3, 2026

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.

1 participant