Skip to content
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

Memory issue with nested results #99

Open
MarinusVonhof opened this issue Aug 7, 2022 · 5 comments
Open

Memory issue with nested results #99

MarinusVonhof opened this issue Aug 7, 2022 · 5 comments

Comments

@MarinusVonhof
Copy link

The validation of large datasets can cause memory-problems. The object nestedResult of class ValidationEngine is not cleaned up when validation of a node is successful.
Adding a cleaning action in createResultFromObject() solved the problem for me:

// Validation was successful. No result.
if (!validationResultObj) {

  // 20220806/mv: Clean the nested results of the report-children
  **if (this.nestedResults[this.recordErrorsLevel + 1]?.length)
    this.nestedResults[this.recordErrorsLevel + 1] = [];**

  return null
}

But, thanks for the good work! Really a nice module.

@tpluscode
Copy link
Collaborator

Hey. Thank you fo reaching out.
I would like to hear how big your data and shapes graphs are. Are you able to provide an example?

@StichtingRIONED
Copy link

Hello. Yes ok, I'll send you some example-files.
They are rather big. For testing-purpose that's ok, but I don't think Javascript is suitable for these large datasets.
A full run takes about 6 hours!

@MarinusVonhof
Copy link
Author

MarinusVonhof commented Oct 7, 2022 via email

@mhusm
Copy link

mhusm commented Dec 5, 2022

I get a maxium call size exceeded for relatively small data sets (2.3mb) and shapes. I'm note sure if this is the same issue. I can't share the data set publicly, though. Tomasz, if you reach out to my corporate email, I could share a bit more.

@mhusm
Copy link

mhusm commented Dec 5, 2022

I've just realized that my problem is likely caused by this issue: #43

I have some reasoning artefacts that lead to cyclic rdfs:subclassOf relationships.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants