-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Flow Classification Rule outcome calculator needs to be direction aware #7036
Comments
Rewrtiting the evaluator to prevent hundreds of database interactions (see step 5). I made a further attempt to speed it up by removing flows which could not be covered by any statement because there are not statements for the flows datatypes. This only reduced the flow population by a small amount, therefore the increased complexity is not worth the minor performance lift. The code I tried (and am now removing is repeated below (just in case!)
|
- re-writing to an in-memory algo rather than lot's of database hits - not ready for prime time - still in a harness #CTCTOWALTZ-3091 finos#7036
- re-writing to an in-memory algo rather than lot's of database hits - not ready for prime time - still in a harness #CTCTOWALTZ-3091 finos#7036
Changes needed (at first glance)
The text was updated successfully, but these errors were encountered: