McManning / McManning/BlueGraph
add a performance page to the wiki
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 256
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
the question i have is “how much do i pay for the convenience of using this graph vs pure c#?”
a page showing bluegraph vs c# benchmarks would help answer.
considerations: allocation pressure, speed loss, cost of graph traversal, cost of graph instantiation.
tests types:
1. data crunch graph like the texture example vs c# equivalent
2. fsm graph vs c# switch case
3. simple branching in bluegrap vs nested ifthenelse in c#
4. instantiating N gameobjects with BG vs with c#
N=10k which helps evaluate BG impact on CPU starved devices
Contributor guide
No contributing guide indexed for this repository
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 the BlueGraph wiki and the texture example referenced in the issue, then define comparable C# cases for the four listed scenarios. The finished page should report BlueGraph versus C# results for allocation pressure, speed, traversal, and instantiation at N=10k, including implications for CPU-starved devices.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, unity
- Domain
- documentation, performance
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100