Performance benefit from using same instance of brush material in WPF 3D graphics

Question

0.00/5 (No votes)

See more:

Hello,

Creating a GeometryModel3D requires a MeshGeometry3D and a Material.

For example,

GeometryModel3D myGeometryModel3D = new GeometryModel3D(myMeshGeometry3D, new DiffuseMaterial(Brushes.Green));

The models I am dealing with can have hundreds or thousands of GeometryModel3D objects. Will it have a performance benefit if I use a single instance of DiffuseMaterial for many GeometryModel3D instances instead of creating a new one for every GeometryModel3D instance?

What I have tried:

GeometryModel3D myGeometryModel3D = new GeometryModel3D(myMeshGeometry3D, new DiffuseMaterial(Brushes.Green))

Posted 16-Mar-17 16:05pm

HD86_

Add a Solution

Comments

Graeme_Grant 16-Mar-17 22:17pm

Have you set up a simple test and tried it?

HD86_ 17-Mar-17 11:30am

No, because I don't know how to detect the difference. I'd like a theoretical answer and not only a practical one. Does creating more brush instances occupy more memory than assigning a single brush to many GeometryModel3D objects?

HD86_ 17-Mar-17 12:38pm

I made the following test: I built several GeometryModel3D objects with the same material. Then I changed the material for one of them and that changed the material for all the other objects that share the same material. Next I built GeometryModel3D objects each with its own material. I changed the material for one object, but the others were not affected. Conclusion: if I use one material instance for each GeometryModel3D instance, that will occupy more memory.

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)