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

Replace futures-timer with tokio_timer #7822

Merged
merged 3 commits into from
May 31, 2019

Conversation

illicitonion
Copy link
Contributor

We now run all our futures on tokio runtimes, so we can do this.

This removes a dep, and in particular, a dep which we had to fork from upstream.

It also means we have one fewer background thread running.

Copy link
Sponsor Member

@stuhood stuhood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hooray!

@stuhood stuhood merged commit a99faa3 into pantsbuild:master May 31, 2019
@stuhood stuhood deleted the dwagnerhall/futures-timer branch May 31, 2019 00:13
illicitonion added a commit that referenced this pull request Jun 4, 2019
illicitonion added a commit to twitter/pants that referenced this pull request Jun 4, 2019
illicitonion added a commit that referenced this pull request Jun 5, 2019
Removing this threadpool introduced a significant performance regression to the `export` goal, for as-yet undiagnosed reasons.

This is a dirty revert of #7822, #7688, and #7685, and adding a tiny commit on top to support thread-local logging.

I will hopefully investigate and re-land fixing up the regression at some point.
illicitonion added a commit that referenced this pull request Jun 5, 2019
Removing this threadpool introduced a significant performance regression to the `export` goal, for as-yet undiagnosed reasons.

This is a dirty revert of #7822, #7688, and #7685, and adding a tiny commit on top to support thread-local logging.

I will hopefully investigate and re-land fixing up the regression at some point.
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.

2 participants