I'm running ctakes both as an API and as a console app. Each time I hit ctakes, the run time per document is getting incrementally slower by a few thousands of a millisecond per xml element (to normalize for different document sizes) than the previous document. Compound this over 1000 documents in 20 minutes and the runs are going from 0.06 milliseconds per xml element to 1.5 milliseconds per xml element. It's a very consistent 0.002 millisecond increase in the rate for each subsequent document I throw at cTAKES.
Is there any caching or garbage collection or something I should be on the lookout to adjust or fix? Thanks ~Alex [cid:image001.jpg@01D96D43.69FD3AA0] Alex Milinovich Director of Research - Data Science Analytics | Quantitative Health Sciences 9500 Euclid Ave. - JJN3 | Cleveland, OH 44195 | m: (216) 245-7655 Please consider the environment before printing this e-mail Cleveland Clinic is currently ranked as the No. 2 hospital in the country by U.S. News & World Report (2017-2018). Visit us online at http://www.clevelandclinic.org for a complete listing of our services, staff and locations. Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you.
