openvino/docs/Extensibility_UG/graph_rewrite_pass.md

OpenVINO Graph Rewrite Pass

@sphinxdirective

.. meta:: :description: Get to know how Graph Rewrite handles running multiple matcher passes on ov::Model in a single graph traversal.

:ref:`ov::pass::GraphRewrite <doxid-classov_1_1pass_1_1_graph_rewrite>``` serves for running multiple matcher passes on :ref:`ov::Model <doxid-classov_1_1_model>``` in a single graph traversal. Example:

.. doxygensnippet:: docs/snippets/template_pattern_transformation.cpp :language: cpp :fragment: [matcher_pass:graph_rewrite]

In addition, GraphRewrite handles nodes that were registered by MatcherPasses during their execution. This nodes will be added to the beginning of the sequence with nodes for pattern matching.

.. note::

When using ``:ref:`ov::pass::Manager <doxid-classov_1_1pass_1_1_manager>``` temporary GraphRewrite is used to execute single MatcherPass.

GraphRewrite has two algorithms for MatcherPasses execution. First algorithm is straightforward. It applies each MatcherPass in registration order to current node.

.. image:: ./_static/images/graph_rewrite_execution.png

But it is not really efficient when you have a lot of registered passes. So first of all GraphRewrite checks that all MatcherPass patterns has type-based root node (it means that type of this node is not hidden into predicate). And then creates map from registered MatcherPasses. That helps to avoid additional cost of applying each MatcherPass for each node.

.. image:: ./_static/images/graph_rewrite_efficient_search.png

.. note::

GraphRewrite execution algorithm cannot be set manually and depends only on root nodes registered inside MatcherPasses.

See Also ########

• :doc:OpenVINO™ Transformations <openvino_docs_transformations>

@endsphinxdirective