[DOC][SYCL][Graph] need warmup before recording if necessary

[guoyejun]

sometimes, the existing code does some extra work which should not be recorded, and so a warmup is needed for this case.

[Bensuo]

Thanks for this addition, this is valuable information but I'm not sure that this is the best place for it. This section is introducing the basic concepts of the API and this is a warning about a very specific usage "gotcha" to watch out for.

In general since the specification is a lengthy already due to the scope of the feature and the potential interactions, I'm wary of adding a lot of usage information like this to the spec. To me this risks both making the spec harder to consume, and making this information harder to find if buried amongst the spec. However, we have had discussions about creating a separate document(s) for more detailed usage information and examples like this.

I'll raise this idea again and see if we can get something set up to capture information like this.

[guoyejun]

hope to see it soon, it is an important guideline for recording the function calls from libraries in the oneapi package such as onednn, onemkl, etc.

[reble]

I agree with @Bensuo by not adding such a guideline to the spec extension. From my perspective, a better place to put interactions with this extension listing workarounds and limitations could be a library documentation.

[guoyejun]

It can be in the library doc at last, but before that, we need a place from sycl side for this guideline.

[EwanC]

A usage guide was created in #14965 and this information added to it, so think this PR can be closed or modified to update the wording in that usage guide if it isn't sufficient.