[intel npu] General NPU optimizations for set_tensor API
#33934
+70
−64
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.
Details:
Loggerobjects in eachintel_npu::Config::get()intel_npu::OptionDesc::get()methods by adding aLoggermember in each of theConfigandOptionDescclassesLoggerclass was refactored to accept onlyconst char*variables for its internal name, ctors/methods usingstd::string_viewandstd::stringparams were explicitly deleted. By normal usage,Loggerobjects get their name statically initialized e.g._logger("ZeroEngineBackend", ...and there would be no need for a runtime name containerstd::string_view->std::stringcopies were found atConfig::get(): const auto it = _impl.find(Opt::key());. Improved my changing internal Config implementation map's key tostd::string_viewstd::string->std::string_viewcovered in "Aggressive" optimization of std::string to std::string_view in configs/properties yet to be discussed as they might be out of scope for the purpose of this PRTickets: