DYN-4229 GraphicDataProvider optimization for repeated calls to get similar object types for tessellation

[saintentropy]

Purpose

https://jira.autodesk.com/browse/DYN-4229

This optimization is to short-circuit the repeated search for and allocation of numerous CLRObjectMarshaller objects during UpdateRenderPackageAsyncTask execution. Right now, within UpdateRenderPackageAsyncTask, we call mirrorData.GetData() for every object we are attempting to tessellate. Within that call, a new instance of an ObjectMarshaller allocated based on the objects type information. This optimization caches the ObjectMarshaller and reuses it if the object type is the same for repeated calls.

Declarations

Check these if you believe they are true

• The codebase is in a better state after this PR
• Is documented according to the standards
• The level of testing this PR includes is appropriate
• User facing strings, if any, are extracted into *.resx files
• All tests pass using the self-service CI.
• Snapshot of UI changes, if any.
• Changes to the API follow Semantic Versioning and are documented in the API Changes document.
• This PR modifies some build requirements and the readme is updated

Reviewers

TBD

FYIs

@jasonstratton @QilongTang

[saintentropy]

In a test graph with a lot of repeated calls to Circle.ByPointRadius this call reduced the time spent in this method from .5s to .07s and also reduced temporary memory allocation by 90%.

[sm6srw]

Great! This looks solid to me. I did spend some time making sure Clear gets called when it should be called and it looks good.

[aparajit-pratap]

Why do these need to be static?

[saintentropy]

They are static because you only need one Interpreter and FFIObjectMarshaller for the GraphicDataProvider class until the runtime is reset. If you made the instances you would allocate permanently an interpreter and marshaller for every mirror data object and that would be worse than temporary allocation

[aparajit-pratap]

I see that the graphicdataprovider member for mirrordata is static too so it looks like there will only be one instance of graphicdataprovider ever but I guess it doesn't hurt to make these static here as well.