You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@olingo.apache.org by "Ralf Handl (JIRA)" <ji...@apache.org> on 2014/03/03 10:22:21 UTC

[jira] [Commented] (OLINGO-184) Performance optimization on edm primitve types

    [ https://issues.apache.org/jira/browse/OLINGO-184?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13917868#comment-13917868 ] 

Ralf Handl commented on OLINGO-184:
-----------------------------------

Which rules exactly are causing the performance problems?

This seems to be a good candidate topic for a "How to implement OData 4.0" committee note at OASIS.

> Performance optimization on edm primitve types
> ----------------------------------------------
>
>                 Key: OLINGO-184
>                 URL: https://issues.apache.org/jira/browse/OLINGO-184
>             Project: Olingo
>          Issue Type: Improvement
>          Components: odata4-commons
>            Reporter: Stephan Klevenz
>            Priority: Minor
>
> Edm primitive types are doing a lot of reg ex checks to be 100% compliant with OData 4.0 specification. These checks are very expensive in CPU consumption. 
> Maybe it is possible to avoid this checks (and instead of OData rules the Java type system rule will take place) or if that is not possible make them optional. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)