Return-Path: <SteveC@ignitemedia.com>
Mailing-List: contact general-help@xml.apache.org; run by ezmlm
Delivered-To: mailing list general@xml.apache.org
Received: (qmail 15542 invoked from network); 1 Nov 2000 20:14:27 -0000
Received: from exchange.ignitemedia.com (HELO georgia.ignitemedia.com)
 (207.24.163.39)
  by locus.apache.org with SMTP; 1 Nov 2000 20:14:27 -0000
Received: by georgia.ignitemedia.com with Internet Mail Service (5.5.2650.21)
	id <WAPLDHH9>; Wed, 1 Nov 2000 14:20:32 -0600
Message-ID: <1AC60639CC71D4118A0B009027AFC9A802F74EA0@georgia.ignitemedia.com>
From: Steve Cohen <SteveC@ignitemedia.com>
To: general@xml.apache.org
Subject: More on problem of transform that is taking too long.
Date: Wed, 1 Nov 2000 14:20:32 -0600 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N

More on the 
This is the line that appears to be the performance-killer:

        <xsl:variable name="months"
select="game[not(year_and_month=preceding-sibling::game/year_and_month)]/yea
r_and_month" />

The point of this is to aid in grouping the schedule by month.  I will then
iterate through the months, outputting all lines belonging to that month.
However, even with all the code that outputs elements commented out, just
executing this line immediately pegs the CPU at 100%.  Remember, the input
is sorted by date.  Why is this simple instruction causing so much delay?
In smaller cases, it doesn't cause this much trouble.