Rel receipe is getting killed after a min or so.

[monWork]

So i have this rel manual receipe to manually annotate spans and relations and my dataset size is just 10mb, so i dont know its getting killed with this error of IOSTREAM.flush time out.

[ryanwesslen]

hi @monWork!

This seems like a memory issue with iPython (Jupyter): Memory Error: IOStream.Flush timed out · Issue #334 · ipython/ipykernel · GitHub

Are you able to run the same command but from a terminal (not a Jupyter notebook)?

As you may have found too, I found this StackOverflow post for a similar issue. The proposed solution was running:

%reset -f

[monWork]

Hi @ryanwesslen
I tried working it through the terminal as well and still the same, the process gets killed after a while. 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 rendering and annotation in the web app. Consider splitting your texts into smaller chunks or sentences.

[ryanwesslen]

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.

relation is responding very slowly

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 …

UI slow when serving snippets over 500 words

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