aws / aws/graph-explorer

Determine the label-count threshold that should trigger the nudge

Open
#2,094 1 comment 0 reactions 0 assignees View on GitHub
internal schema wayfinder:research
Dominant language
TypeScript
Stars
481
Forks
108
Avg merge
6d 8h
Merged PRs (30d)
5

Description

## Question

What combined unique node+edge label count should trigger the nudge?

Gather inputs and recommend a starting threshold (10k is a placeholder):
- Any Neptune / graph data-modeling guidance on label cardinality.
- The point at which GE's current schema sync + label-scale UI actually degrade.
- How the pending scaling fixes (#2076, #2077, #2086) move that point.

---

> [!IMPORTANT]
> Internal only — this issue is maintained by the core team and is not accepting external contributions.

Contributor guide

Open the contributing guide

Research direction

No files, tests, or entry points are named. Review the Neptune and graph data-modeling guidance, assess where schema sync and the label-scale UI degrade, and account for scaling fixes #2076, #2077, and #2086; done means recommending a starting combined unique node+edge label threshold instead of the 10k placeholder.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
data-visualization, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.