# Polyvalent templates vs multiple templates **URL:** \ **Category:** Ignition\ **Created:** [May 31, 2016, 6:38pm UTC](https://forum.inductiveautomation.com/t/polyvalent-templates-vs-multiple-templates/11753 "2016-05-31T18:38:06Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Philcr](https://avatars.discourse-cdn.com/v4/letter/p/e99b99/32.png) [@Philcr](https://forum.inductiveautomation.com/u/Philcr)\ **Post date:** [May 31, 2016, 6:38pm UTC](https://forum.inductiveautomation.com/t/polyvalent-templates-vs-multiple-templates/11753/1 "2016-05-31T18:38:06Z")
Hello, does someone knows if making polyvalent templates, like one template with multiple custom properties to make multiple display (rotation, reflexion, visible,etc.), can make a project to run slower because I must make multiple instances of shape, so multiple color binding running in the background. Doing this reduces the number of template greatly, and I find it much easier to work with. Should I avoid this method and make multiple template instead? Thank you ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [May 31, 2016, 7:26pm UTC](https://forum.inductiveautomation.com/t/polyvalent-templates-vs-multiple-templates/11753/2 "2016-05-31T19:26:25Z")
It will certainly load slower, as there are more total objects in any display built that way. And it’ll use more memory. If there are animating bindings that would be updating on the hidden parts, then it’ll run slower, too. You simply have to balance the memory and performance impact against the maintenance effort of multiple templates. Unless there are many hundreds, I’d use multiple templates. You can programmatically swap them on the template holder and/or template canvas to get the equivalent of polymorphism.