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

[Performance] How to close this "Begin execution" log #18110

Closed
ttandqq opened this issue Oct 26, 2023 · 6 comments
Closed

[Performance] How to close this "Begin execution" log #18110

ttandqq opened this issue Oct 26, 2023 · 6 comments
Labels
quantization issues related to quantization stale issues that have not been addressed in a while; categorized by a bot

Comments

@ttandqq
Copy link

ttandqq commented Oct 26, 2023

Describe the issue

I find that when I call ORT::session::Run function, the log "Begin execution" always be reported. I have call SetRunLogSeverityLevel and SetRunLogVerbosityLevel to set the level to ORT_LOGGING_LEVEL_WARNING,but still can not close the log report.

I think too many logs can affect the performance of predict.

To reproduce

Ort::RunOptions runOptions{};
runOptions.SetRunLogSeverityLevel(ORT_LOGGING_LEVEL_WARNING);
runOptions.SetRunLogVerbosityLevel(ORT_LOGGING_LEVEL_WARNING);

m_session.Run(runOptions, xx);

Urgency

No response

Platform

Linux

OS Version

Ret Hat

ONNX Runtime Installation

Built from Source

ONNX Runtime Version or Commit ID

the newest version

ONNX Runtime API

C++

Architecture

X64

Execution Provider

Default CPU

Execution Provider Library Version

No response

Model File

No response

Is this a quantized model?

Yes

@github-actions github-actions bot added the quantization issues related to quantization label Oct 26, 2023
@ttandqq
Copy link
Author

ttandqq commented Oct 26, 2023

image

@ttandqq
Copy link
Author

ttandqq commented Oct 26, 2023

ONNX Runtime Versionn is 14.1

@pranavsharma
Copy link
Contributor

That line is logged under verbose mode. You don't need to set any log level as the default is warning.

@ttandqq
Copy link
Author

ttandqq commented Oct 27, 2023

That line is logged under verbose mode. You don't need to set any log level as the default is warning.

But If I do not set any log level, thest logs still be reported. I do not think these are Warning or Error level.
image

And this line is still reported.
image

Copy link
Contributor

This issue has been automatically marked as stale due to inactivity and will be closed in 7 days if no further activity occurs. If further support is needed, please provide an update and/or more details.

@github-actions github-actions bot added the stale issues that have not been addressed in a while; categorized by a bot label Nov 26, 2023
Copy link
Contributor

github-actions bot commented Jan 4, 2024

This issue has been automatically closed due to inactivity. Please reactivate if further support is needed.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
quantization issues related to quantization stale issues that have not been addressed in a while; categorized by a bot
Projects
None yet
Development

No branches or pull requests

2 participants