Return-Path: Delivered-To: apmail-incubator-uima-user-archive@locus.apache.org Received: (qmail 7353 invoked from network); 11 Jul 2007 17:39:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Jul 2007 17:39:55 -0000 Received: (qmail 95625 invoked by uid 500); 11 Jul 2007 17:39:58 -0000 Delivered-To: apmail-incubator-uima-user-archive@incubator.apache.org Received: (qmail 95515 invoked by uid 500); 11 Jul 2007 17:39:58 -0000 Mailing-List: contact uima-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: uima-user@incubator.apache.org Delivered-To: mailing list uima-user@incubator.apache.org Received: (qmail 95506 invoked by uid 99); 11 Jul 2007 17:39:57 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jul 2007 10:39:57 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [204.127.192.83] (HELO rwcrmhc13.comcast.net) (204.127.192.83) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jul 2007 10:39:54 -0700 Received: from rmailcenter19.comcast.net ([204.127.197.129]) by comcast.net (rwcrmhc13) with SMTP id <20070711173933m130053pvie>; Wed, 11 Jul 2007 17:39:33 +0000 Received: from [67.180.48.10] by rmailcenter19.comcast.net; Wed, 11 Jul 2007 17:39:32 +0000 From: holmberg2066@comcast.net (greg@holmberg.name) To: uima-user@incubator.apache.org, uima-user@incubator.apache.org Cc: "Adam Lally" Subject: Re: Why XmiCasSerializer is slow Date: Wed, 11 Jul 2007 17:39:32 +0000 Message-Id: <071120071739.18013.469515D40009E2210000465D2206998499C0C0CFCD099D0A0D03040108@comcast.net> X-Mailer: AT&T Message Center Version 1 (Oct 4 2006) X-Authenticated-Sender: aG9sbWJlcmcyMDY2QGNvbWNhc3QubmV0 X-Virus-Checked: Checked by ClamAV on apache.org > Also perhaps we can drastically reduce the number of times the > serializer calls this method. Among other places, it looks like it is > called by Type.isArray, which is in turn called by > TypeSystem.subsumes. I'd have to run a test with the XmiCasSerializer > to see what the real call stack looks like. Here's the call stack of the most expensive path, in case it helps: XmiCasSerializer$XmiCasDocSerializer. CASImpl.ll_getTypeClass(int) TypeSystemImpl.subsumes(int, int) TypeSystemImpl.ll_subsumes(int, int) TypeSystemImpl.ll_isArrayType(int) TypeSystemImpl.ll_isValidTypeCode(int) SymbolTable.getSymbol(int) Vector.get(int) Greg Holmberg