• State Not Answered
  • Replies 3 replies
  • Subscribers 21 subscribers
  • Views 379 views
  • Users 0 members are here
Options
Related

OMI Namespace Sizing

Phil Wood

Has anyone run into any issues around namespace sizing in OMI?  I'm in the process of developing a batch layout for a customer, and working with that I've run into a scenario where I have a lot of namespace attributes (around 80).  Recently I have run into an issue where it seems like nothing on my namespace seems to be working; writes do not occur to the namespace, proven via logmessage, many (not all) values show up as NaN.  I have a support call in but figured I'd reach out to the greater braintrust and see if anyone has run into a block like this.  I'm on 2023 P04 in this case. 

Parents
  • 0

    Hi Phil, we have used Namespaces with about 80 attributes without any issues so it might be some other factor in play here.

    So It would be interesting to see what you find out during your support session.

    I do like the possibility to use several namespaces for a setup, but mostly due to the advantage of structured naming conventions and that you can not have several developers working on the same checked out namespace.

    Natural splits such as based on specific features, such as
    User-relates settings, Global Settings, Recipe data, etc..

    Plays very nicely in my experience, but if there are known performance related limitations it would be super interesting to know.

  • 0 in reply to Richard Köhlerstrand

    Another comment, if there is a very large amount of structured data that has to be stored, I have also used alternative methods to store them in strings defined in the namespace, such as json strings, or csv (if used for Graphic Repeater), instead of a large namespace, parsing the content for use can be done quite efficiently in the symbol.

Reply Children
No Data