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

Any plan to support TBB 2021.1.1 #2039

Closed
sunpoet opened this issue Jan 23, 2021 · 3 comments
Closed

Any plan to support TBB 2021.1.1 #2039

sunpoet opened this issue Jan 23, 2021 · 3 comments

Comments

@sunpoet
Copy link

sunpoet commented Jan 23, 2021

task_scheduler_init is deprecated and being removed in TBB 2021.1.1. Is there any plan to support newer TBB?
Thanks.

@eddelbuettel
Copy link
Member

Please see HISTORY.md. From the 2.1.0 release:

@Shelnutt2
Copy link
Member

Shelnutt2 commented Jan 23, 2021

Hello @sunpoet , as @eddelbuettel has pointed out, we have disabled the use of TBB by default and will likely be removing support for it in the an upcoming release over the next couple months. As such we don't plan to upgrade the version at this time.

We've replaced the use of TBB with our own internal threadpool implementation that uses standard C++ threading. While TBB provided a nice workpool implementation and good concurrency primitives, we did have a number of issues with it. The two major issues that led us to work to remove it was:

  1. The thread pool size could only be initialized once per process. This means in long-lived applications like MariaDB, or python shells a user couldn't adjust the TBB thread count over time or based on work load without restarting the process.
  2. TBB did not like the main process being forked, this caused problems with python multi-process concurrency models and with packages like dask.

@sunpoet
Copy link
Author

sunpoet commented Jan 23, 2021

@eddelbuettel @Shelnutt2 Thanks for the quick and detailed answer. Currently the FreeBSD port databases/tiledb is built with TBB enabled unconditionally. I'll disable it later.

@sunpoet sunpoet closed this as completed Jan 23, 2021
uqs pushed a commit to freebsd/freebsd-ports that referenced this issue Jan 26, 2021
- Bump PORTREVISION for dependency change

Upstream has disabled the use of TBB by default and will likely be removing
support for it in the an upcoming release over the next couple months. They
also replaced the use of TBB with their own internal threadpool implementation
that uses standard C++ threading.

Reference:	TileDB-Inc/TileDB#2039


git-svn-id: svn+ssh://svn.freebsd.org/ports/head@562732 35697150-7ecd-e111-bb59-0022644237b5
uqs pushed a commit to freebsd/freebsd-ports that referenced this issue Jan 26, 2021
- Bump PORTREVISION for dependency change

Upstream has disabled the use of TBB by default and will likely be removing
support for it in the an upcoming release over the next couple months. They
also replaced the use of TBB with their own internal threadpool implementation
that uses standard C++ threading.

Reference:	TileDB-Inc/TileDB#2039
Jehops pushed a commit to Jehops/freebsd-ports-legacy that referenced this issue Jan 26, 2021
- Bump PORTREVISION for dependency change

Upstream has disabled the use of TBB by default and will likely be removing
support for it in the an upcoming release over the next couple months. They
also replaced the use of TBB with their own internal threadpool implementation
that uses standard C++ threading.

Reference:	TileDB-Inc/TileDB#2039


git-svn-id: svn+ssh://svn.freebsd.org/ports/head@562732 35697150-7ecd-e111-bb59-0022644237b5
svmhdvn pushed a commit to svmhdvn/freebsd-ports that referenced this issue Jan 10, 2024
- Bump PORTREVISION for dependency change

Upstream has disabled the use of TBB by default and will likely be removing
support for it in the an upcoming release over the next couple months. They
also replaced the use of TBB with their own internal threadpool implementation
that uses standard C++ threading.

Reference:	TileDB-Inc/TileDB#2039
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

3 participants