Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[performance] feed_to_graph_path is slow on larger feeds

See original GitHub issue

test_feed_to_graph_path itself is the slowest test by far. Create benchmarks and identify which steps are slowest. Find ways to speed up operations and get graph creation process to be as fast as possible.

Issue Analytics

State:
Created 6 years ago
Comments:11 (10 by maintainers)

Top GitHub Comments

2reactions

kuanbcommented, Jul 12, 2018

Huge performance gain found right here: https://github.com/kuanb/peartree/issues/87

(Thank you @yiyange)

1reaction

kuanbcommented, Jul 16, 2018

LA Metro (without digging around for the exact numbers) used to take 12-15 minutes.

It now takes: Without MP: 231s With MP: 229s

So, no observable improvement. Of course, it’s running in a Docker environment that only has access to 2 CPUs on my '16 Macbook Pro. A better test would be to use a virtual machine on AWS / GCloud or wherever and see what gains are achieved there.

That said, we can observe that there are pretty limited (essentially no observable) gains to be had by MP for the typical user/use case (local machine, in a Notebook like environment). This is something that should be addressed long term.