OData | enables exposing REST APIs for Open Data clients | REST library

Looking at the result of Cachegrind, it doesn't look like the memory is your bottleneck. The NN has to be stored in memory anyway, but if it's too large that your program's having a lot of L1 cache misses, then it's worth thinking to try to minimize L1 misses, but 1.7% of L1 (data) miss rate is not a problem.

So you're trying to make this run fast anyway. Looking at your code, what's happening at the most inner loop is very simple (load-> multiply -> add -> store), and it doesn't have any side effect other than the final store. This kind of code is easily parallelizable, for example, by multithreading or vectorizing. I think you'll know how to make this run in multiple threads seeing that you can write code with some complexity, and you asked in comments how to manually vectorize the code.

I will explain that part, but one thing to bear in mind is that once you choose to manually vectorize the code, it will often be tied to certain CPU architectures. Let's not consider non-AMD64 compatible CPUs like ARM. Still, you have the option of MMX, SSE, AVX, and AVX512 to choose as an extension for vectorized computation, and each extension has multiple versions. If you want maximum portability, SSE2 is a reasonable choice. SSE2 appeared with Pentium 4, and it supports 128-bit vectors. For this post I'll use AVX2, which supports 128-bit and 256-bit vectors. It runs fine on your CPU, and has reasonable portability these days, supported from Haswell (2013) and Excavator (2015).

The pattern you're using in the inner loop is called FMA (fused multiply and add). AVX2 has an instruction for this. Have a look at this function and the compiled output.

Rootcause has been identified as submitter property wasn't created with flag refinable

Edit: As @Olivier mentions, my original answer referred to OData in .NET and not Olingo.

Unfortunately as you probably have found out yourself, the standard Olingo documentation doesn't answer this particular question directly, though it does mention support for lazy-loading and streaming behaviour (which would not make any sense to filter on the application level).

However, you would be hard-pressed to find an ORM or DB Adapter nowadays that does not support filtering on the database level, as this will almost always be faster than doing so in your application for non-trivial workloads.

I will try to update this answer with a more authorative source.

(original answer)

According to this analysis:

As long as your data provider supports deferred queries and you don't force evaluation by calling something like .ToList(), the query will not be evaluated until the OData filters are applied, and they'll be handled at the database level.

I recently faced the similar problem. I get the solution by

• removing odata service injection from startup file (because swagger automatically add metadata classes if I tried to inject odata from startup)
• downgrading OData from 8.0.4 to 8.0.0
• and implementing ODataQueryOptions inside controller instead of EnableQuery actionfilter
• used ODataBuilder/OdataModelBuilder within controller instead of startup. in my case it is ODataBuilder

So after 5 days of internal OData debugging I managed to get it to work. Here are the necessary steps:

First remove all OData calls/attributes from your controller/configure services which might do funky stuff (ODataRoutingAttribute or AddOData())

Create a simple asp.net controller with the route to your liking and map it in the endpoints

Try this:

Update This is only supported for Microsoft.OData.Core versions >= 7.9.4 based on this pr.

You should be able repeat the same filter criteria in your $orderby that you have in your $expand to get what you are looking for.

When you publish the OData interface, you use a special data processor to specify what data will be available through the REST API. Since additional attributes of objects in typical 1C programs are usually stored in the "AdditionalAttributesAndInfoSets" catalog, try to open access via the REST API for this catalog as well. You can see an article on working with OData: https://1c-dn.com/blog/synchronization-between-a-mobile-app-and-a-database-server-on-the-1c-platform/

The error is that you are trying to access an index that does not exist in the array because of <= in the for loop, try to use < when you use .length of an array.