-
Notifications
You must be signed in to change notification settings - Fork 260
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
Validation slow for typed dimension tables in Solvency2 #217
Comments
@alexdejong1723 We will begin an initial investigation into the slow performance on this next week. Thanks for the heads up and we will let you know the result of our investigation and resulting improvements. |
@alexdejong1723 A quick update on our investigation. We have zeroed in on a filtering function that is operating really slow. We are analyzing what we can do to fix/rewrite/change the function to improve performance. |
When do you expect this to be fixed / implemented? |
@vivet we don't have an exact timeline yet, but I'll make sure this issue is updated when we do. |
As of the latest release of Arelle 2.5.8 we've managed to cut the formula execution time for this taxonomy in half. Still not nearly as fast as Altova, but likely as fast as we can get at the moment given the current platform limitations (Python). We have some longer term plans that could potentially close the gap. |
When validating XBRL files containing dynamic tables like in Solvency2 or CRDIV, the validation takes significantly more time than other validation tools. I created a test to reproduce this issue using the S.06.02.01 tables in Solvency2:
I added two tests. One with 10 lines and one with 1000 lines. The file containing 10 lines is validated relatively quickly, but the one containing 1000 lines will take a significant amount of time (after 30 minutes I stopped the process). Meanwhile, a validation tool like Altova validates that file in a couple of seconds.
2.6.0.zip
I have used version 1.2022.05.27 64-bit for these tests.
The text was updated successfully, but these errors were encountered: