There are 2 APIs when working with UIMA: 1) The APIs for Annotator components
2) The APIs used to "embed" a UIMA Pipeline into something else. The basic flow for #2 includes: a) Feeding XML Descriptors of the UIMA pipeline to be instantiated to the UIMA Framework, producing an "analysis engine", etc.; this action has a secondary effect of invoking the "initialize" method on all the parts. The initialize method can be implemented by any part to do any setup it wants, including loading other resources. b) Running things through the pipeline, usually in a loop. HTH. See for more details: http://uima.apache.org/d/uimaj-2.4.0/tutorials_and_users_guides.html Chapter 3 talks about the embedding application and the APIs used there. -Marshall On 7/19/2013 5:15 AM, swirl wrote: > Marshall Schor <msa@...> writes: > >> >> On 7/16/2013 10:38 PM, swirl wrote: >>> I am wrapping a Uima analysis engine in a Tomcat. >>> >>> This AE loads and parses a large model file (300Mb). >>> The loading time of this model takes 3min. This is unacceptable if users > have >>> to wait so long to do analysis on one document. >>> >>> What are the possible ways to reduce the loading time? >> The basic UIMA lifecycle includes the possibilities of loading the model > at >> "startup" time, and then leaving it loaded. Would this work for your > case? No >> need for UIMA-AS, here. The pipeline would be loaded and "waiting" to > receive a >> CAS to work on; the model would be retained in memory between calls to > process(). > > > Thanks Marshall, > I am intrigued by the possibility of Uima framework loading the model at > "startup" time, can you point out to me where I can start looking for this > function? > > >
