On Tue, Jul 8, 2008 at 4:32 PM, Thilo Goetz <[EMAIL PROTECTED]> wrote:
> Precisely. It's an implementation detail of the CAS heap that > we should be able to change -- that we must be able to change > if we would like to improve on the heap. The CAS heap and > in particular the way it grows is a major performance bottleneck > for large documents. If we have other parts of UIMA depend on > the (bad) implementation details now, we'll never be able to > improve on the design. Can you give details on how CAS heap growth is a major bottleneck for large documents? Do we have specific scenarios that can be used to measure current heap performance and potential fixes?
