Optimize recipe search by checking against last cached recipe before anything else #47
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Firstly, auto crafting tables can cause a performance impact when used very often in large farms.
The main reason for this is due to the recipe lookup, which searches through all recipes.
So what I did was use the already existing last recipe, and attempt to check it first. This is a great performance boost since it drastically speeds up all the auto crafting tables in farms.
old = current state, new = with cache
Accidentally left the one with cache running for 10 seconds longer than the old one (after tick warp), either way, it shows the point.
As you can also see, the extra match against the last cache added 62ms to the total checks which are nearly negligible. So adding 62ms to all auto crafting tables is worth it for the performance boost that this offers.