Validating a deeply nested schema using custom "strict" draft 2020 metaschema can be very slow about check-jsonschema HOT 3 CLOSED

I think this might have been a slight miscommunication on the jsonschema ticket in question, so I've replied there where it will be more visible to jsonschema. But I'm going to leave this open until we know the cause a bit better. It may be that check-jsonschema can and should optimize its usage of jsonschema (in which case the ticket belongs here), or it may be that this is a slow case for jsonschema inherently or some other issue.

On my machine, I was able to validate your example document, but it did take 5 minutes 58 seconds wall time.

from check-jsonschema.

Fixed in python-jsonschema/jsonschema#1097

from check-jsonschema.

It's only 80% of the way fixed, I would say. 😅
check-jsonschema isn't using the new (faster) implementation from jsonschema yet. But it's an active work in progress.

I plan to check this example after the updates are done and see how it performs.

So please, keep an eye out for a future release which refers to the new referencing implementation!

from check-jsonschema.