Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Figure out why pathing got 30% faster in the last few days? #168

Closed
leijurv opened this issue Sep 15, 2018 · 0 comments
Closed

Figure out why pathing got 30% faster in the last few days? #168

leijurv opened this issue Sep 15, 2018 · 0 comments

Comments

@leijurv
Copy link
Member

leijurv commented Sep 15, 2018

2018-09-14_18 22 25
The TODO here is to bisect the commits and figure out how this happened?

I just randomly glanced at the number of nodes considered and it was higher than ever before!

This is the log

[18:22:00] [Thread-224/INFO]: [CHAT] §5[§dBaritone§5]§7 Starting to search for path from BlockPos{x=1368, y=68, z=457} to Goal{x=0,z=0}
[18:22:04] [Thread-224/INFO]: [STDOUT]: 6116433 movements considered
[18:22:04] [Thread-224/INFO]: [STDOUT]: Open set size: 128991
[18:22:04] [Thread-224/INFO]: [STDOUT]: 90486 nodes per second
[18:22:04] [Thread-224/INFO]: [CHAT] §5[§dBaritone§5]§7 Took 4000ms, A* cost coefficient 1.5, 6116433 movements considered
[18:22:04] [Thread-224/INFO]: [STDOUT]: Path goes for 245.63387388550464 blocks
[18:22:04] [Thread-224/INFO]: [CHAT] §5[§dBaritone§5]§7 Static cutoff 272 to 244
[18:22:04] [Thread-224/INFO]: [CHAT] §5[§dBaritone§5]§7 Found path segment from BlockPos{x=1368, y=68, z=457} towards Goal{x=0,z=0}. 361945 nodes considered

SIX MILLION MOVEMENTS IN FOUR SECONDS ON MY LAPTOP?!?!??!

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

No branches or pull requests

1 participant