ryanwesslen
September 27, 2022, 7:20pm
4
hi @monWork !
monWork:
However, one thing i wanted to notify you is that the annotation examples are whole documents with good length. Could that be the reason for it ?
I do see this warning ⚠ Long example with 588 tokens detected. This can potentially lead to slower render
Very likely. This is a well known issue.
Hi and sorry about this – it's currently expected that the interface becomes less performant for very long documents with many tokens, and we're working on a rewrite that doesn't have this problem. I think what makes it additionally tricky in your case is that you just end up with more tokens overall, due to the way the characters are segmented.
As a workaround, one thing you can do is use patterns to disable all tokens that you know won't ever be part of a relation – of course, only if that's …
Hi! Which annotation interface are you using? Are you using the relations UI? If so, that can currently become slower with larger documents (the specifics also depend on your browser and machine). I definitely want to work on improving the performance here – the tricky part is that the interface is quite complex so we might need a better way to represent the tokens and spans (which technically all have to be able to be connected to any other token or span).
If you're using any other text-based …
Try disabling tokens (--disable-patterns) for terms you don't need for labeling (this will speed up some). Or alternatively, could you break up your documents into sentences? Let me know if you need help