refactor: add Rbush/Flatbush impl in SegmentTree

[akhilender-bongirwar]

fixes #102
/claim #102

2025-04-26.16-00-44.mp4

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
capacity-node-autorouter	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 31, 2025 4:50pm

[seveibar]

@akhilender-bongirwar nice video, clearly shows the difference! on a plane so might be a bit before merge. Can you confirm there are no new DRC errors? (DRC errors check that the implementation is correct by making sure lines don't overlap improperly)

Personally I like to always check against keyboard5 because it tends to catch any subtle bugs. tyty!!!

[seveibar]

Keyboard 3 is also a good one if keyboard5 is too slow to run for you.

I got 7.5s on main vs 7s on your branch AWESOME /tip $10

[algora-pbc]

🎉🎈 @akhilender-bongirwar has been awarded $10 by tscircuit! 🎈🎊

[algora-pbc]

Please visit Algora to complete your tip via Stripe.

[seveibar]

It seems like there may be performance degradation again. Compare this page with your branch? You can also slow down your CPU using the performance tab to help get worse, more measurable time

https://unraveller.vercel.app/?fixtureId=%7B%22path%22%3A%22examples%2Fsimplified-path-solver%2Fsimplifiedpathsolver8.fixture.tsx%22%7D

[akhilender-bongirwar]

It seems like there may be performance degradation again. Compare this page with your branch? You can also slow down your CPU using the performance tab to help get worse, more measurable time

https://unraveller.vercel.app/?fixtureId=%7B%22path%22%3A%22examples%2Fsimplified-path-solver%2Fsimplifiedpathsolver8.fixture.tsx%22%7D

2025-04-27.00-44-44.mp4

@seveibar please check

[akhilender-bongirwar]

@akhilender-bongirwar nice video, clearly shows the difference! on a plane so might be a bit before merge. Can you confirm there are no new DRC errors? (DRC errors check that the implementation is correct by making sure lines don't overlap improperly)

Personally I like to always check against keyboard5 because it tends to catch any subtle bugs. tyty!!!
Keyboard 3 is also a good one if keyboard5 is too slow to run for you.

Thank you. Sure, here it is

2025-04-27.00-49-43.mp4

[akhilender-bongirwar]

@seveibar why aren't the workflows running?

[seveibar]

@akhilender-bongirwar not sure, will be looking at this later today, thanks for the vid, definitely helps!!

[akhilender-bongirwar]

@akhilender-bongirwar not sure, will be looking at this later today, thanks for the vid, definitely helps!!

@seveibar, works now

[seveibar]

Some delays getting to this, if you can show it has a large performance impact via a side-by-side screenshot with https://unraveller.vercel.app (before/after), then I can merge, otherwise need to turn to some important cache optimizations, we will eventually get this in either way most likely!!!

[akhilender-bongirwar]

1. Keyboard3

• Before

Time taken: 23.240s

• After

Time Taken: 22.854s

2. Keyboard5

• Before
  

Time taken: 25.044s

• After

Time taken: 23.532s

3. SimplifiedPathSolver5

• Before

Time taken: 0.232s

• After

Time taken: 0.116s

[akhilender-bongirwar]

Some delays getting to this, if you can show it has a large performance impact via a side-by-side screenshot with https://unraveller.vercel.app (before/after)

cannot tell large performance impact but the above are the before/after results. Do you want me to add any other components screenshots too?

[akhilender-bongirwar]

@seveibar sorry for delay I was busy with my end semester exams. Please let me know if any further changes are required here

[seveibar]

@akhilender-bongirwar yes sorry for the delay, im going to be working to merge this in the next couple days

[akhilender-bongirwar]

@seveibar please check

[akhilender-bongirwar]

@seveibar please check

cc @seveibar

[seveibar]

@akhilender-bongirwar sprry for the delay, on the issues tab we currently have some major bugs so im trying to be careful to not switch the implementation and accidentally introduce new ones