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

Tuned example handling #85

Merged
merged 2 commits into from
Jul 16, 2022
Merged

Tuned example handling #85

merged 2 commits into from
Jul 16, 2022

Conversation

daveshanley
Copy link
Owner

Now exponentially faster using async design.

not sure why I set these as not recommended?
This damn rule has been the slowest since I wrote it. I don't like that I combined everything in here, but it is what it is for now. I managed to speed things up by running every schema operation async. This creates god knows how many thens of thousands more threads, but it completly unblocks the rule at scale.

This rule is now super fast. I could get faster, but it's topping the charts for right now. Timeout in schema resolving increased to 500ms as it was tripping at lowerspeeds and creating random result counts.
@daveshanley daveshanley merged commit abc1c11 into main Jul 16, 2022
@daveshanley daveshanley deleted the example-tuning branch July 16, 2022 12:54
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

Successfully merging this pull request may close these issues.

None yet

1 participant