Next in thread → Next in month →

Re: key ambiguity check

From
James Clark <>
Date
2001-07-28T03:55:28+00:00
ID
4180167798.996317613@guava
Thread
Re: key ambiguity check
> Maybe it was because of my poor implementation, but I recorded that
> almost 80% of the parsing time is spent to enforce the key ambiguity
> check. That is, enforcing this check makes schema parsing 5 times slower.
>
>
> I'm curious how it is like in Jing.

I measured 40%.  That is a lot, but I haven't done any optimization on 
key-ambiguity checking at all.  I also haven't yet implemented all the 
checks in 7.1 or the check on key/keyRef datatype consistency.  So I don't 
think this figure is very meaningful.

James
Next in thread → Next in month →