feat!: RunAsyncを使う
#889
Merged
feat!: RunAsyncを使う
#889
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
qryxip
force-pushed
the
feat-use-run-async
branch
from
ea7ee70 to
ac6ca3f
Compare
Hiroshiba
approved these changes
Dec 9, 2024
|
同期版は あれ |
|
おお了解です！！同期版はRunの方を使う設計、良さそう！ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
内容
非同期APIにおける推論に
ort::Session::run_asyncを使うようにする。これにより、推論がキャンセル可能になる。#888 の影響を受け推論が失敗するので、CIを通すため、Python APIのテストとexampleについては（すべてのプラットフォームで）
cpu_num_threads=max(multiprocessing.cpu_cout(), 2)とする。BREAKING-CHANGE: 非同期APIにおいて、INTRA Thread Countが
1だと推論がすべてエラーになるようになる。関連 Issue
Resolves #687.
Refs: VOICEVOX/ort#11
その他