[jira] Created: (XALANJ-2530) Poor performance transforming from SAX to DOM with large text content

Poor performance transforming from SAX to DOM with large text content - Key: XALANJ-2530 URL: https://issues.apache.org/jira/browse/XALANJ-2530 Project: XalanJ2 Issue Type

[jira] Commented: (XALANJ-2502) Some serious performance issues with XPathAPI processing

you are guaranteeing that the DOM trees supplied do not change; the implementation of CachedXPathAPI will build a DTM instance for any given DOM tree only one time. I hope that helps. > Some serious performance issues with XPathAPI processing >

[jira] Created: (XALANJ-2502) Some serious performance issues with XPathAPI processing

Some serious performance issues with XPathAPI processing Key: XALANJ-2502 URL: https://issues.apache.org/jira/browse/XALANJ-2502 Project: XalanJ2 Issue Type: Bug Security Level

[jira] Created: (XALANJ-2500) Terrible performance from ToStream.startPrefixMapping calling flush() repeatedly while serializing XML

Terrible performance from ToStream.startPrefixMapping calling flush() repeatedly while serializing XML -- Key: XALANJ-2500 URL: https://issues.apache.org/jira

Bad performance / race condition?

attempting a lot of classloading on each and every request seems very expensive. Any thoughts? - http://www.davidkarlsen.com -- View this message in context: http://www.nabble.com/Bad-performance---race-condition--tp19518724p19518724.html Sent from the Xalan - Dev mailing list a

[jira] Resolved: (XALANC-660) Compilation errors in Tests/Performance/TestHarness.hpp on some platforms

[ https://issues.apache.org/jira/browse/XALANC-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bertoni resolved XALANC-660. -- Resolution: Fixed Patch applied. > Compilation errors in Tests/Performance/TestHarness.hpp

[jira] Created: (XALANC-660) Compilation errors in Tests/Performance/TestHarness.hpp on some platforms

Compilation errors in Tests/Performance/TestHarness.hpp on some platforms - Key: XALANC-660 URL: https://issues.apache.org/jira/browse/XALANC-660 Project: XalanC Issue

[jira] Resolved: (XALANJ-2375) Poor performance parsing and evaluating XPath expressions

[ https://issues.apache.org/jira/browse/XALANJ-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henry Zongaro resolved XALANJ-2375. --- Resolution: Fixed Applied the patch to Subversion repository. > Poor performance pars

[jira] Commented: (XALANJ-2375) Poor performance parsing and evaluating XPath expressions

[ https://issues.apache.org/jira/browse/XALANJ-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486036 ] Christine Li commented on XALANJ-2375: -- The patch looks good. Should resolve the problem. > Poor performa

[jira] Commented: (XALANJ-2375) Poor performance parsing and evaluating XPath expressions

(//node()) 50 times, and 15016ms to evaluate the same expression against the sample input document 3 times. [1] http://issues.apache.org/jira/secure/attachment/12354609/testJ2375.zip > Poor performance parsing and evaluating XPath expressi

[jira] Created: (XALANJ-2375) Poor performance parsing and evaluating XPath expressions

Poor performance parsing and evaluating XPath expressions - Key: XALANJ-2375 URL: https://issues.apache.org/jira/browse/XALANJ-2375 Project: XalanJ2 Issue Type: Bug

[jira] Resolved: (XALANC-629) Performance improvements for text node stripping

[ https://issues.apache.org/jira/browse/XALANC-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bertoni resolved XALANC-629. -- Resolution: Fixed Patch applied. > Performance improvements for text node stripp

[jira] Resolved: (XALANC-638) Performance test program does not build on HP-UX

[ https://issues.apache.org/jira/browse/XALANC-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bertoni resolved XALANC-638. -- Resolution: Fixed Patch applied. > Performance test program does not build on HP

[jira] Commented: (XALANJ-2368) Performance: UTF-8 writer byte[] and char[] buffers should be reused

nternal buffer is full of characters is full, or at the end when the writer is flushed. This leaves the WriterToUTF8Buffered object in full control of its internal ugly buffers. I'll be attaching a patch soon. > Performance: UTF-8 writer byte[] an

[jira] Created: (XALANJ-2368) Performance: UTF-8 writer byte[] and char[] buffers should be reused

Performance: UTF-8 writer byte[] and char[] buffers should be reused Key: XALANJ-2368 URL: https://issues.apache.org/jira/browse/XALANJ-2368 Project: XalanJ2 Issue Type

[jira] Commented: (XALANC-629) Performance improvements for text node stripping

[ https://issues.apache.org/jira/browse/XALANC-629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12473579 ] Ashley Zinyk commented on XALANC-629: - I checked out the patch. It looks good to me. > Performa

[jira] Created: (XALANC-638) Performance test program does not build on HP-UX

Performance test program does not build on HP-UX Key: XALANC-638 URL: https://issues.apache.org/jira/browse/XALANC-638 Project: XalanC Issue Type: Bug Components: XalanC Affects

[jira] Created: (XALANC-629) Performance improvements for text node stripping

Performance improvements for text node stripping Key: XALANC-629 URL: https://issues.apache.org/jira/browse/XALANC-629 Project: XalanC Issue Type: Bug Components: XalanC Affects

RE: Performance problem for Xalan-J on intel-dual core

Robert, the bulk of these synchronization/performance fixes (mostly from Toadie) will be in 2.7.1 to be release. The 2.7.1 release will be out Friday November 24, 2006 if all goes well. A number of similar patches from Dave Brosius were also applied, although the performance implications of his

Re: Performance problem for Xalan-J on intel-dual core

Vector, or other old over-synchronization will probably be left alone unless it is a performance issue. - Brian [EMAIL PROTECTED]

Re: Performance problem for Xalan-J on intel-dual core

We've known for a while that some part of Xalan are oversynchronized, due to their use of the original Java heap and vector classes -- but we couldn't move to the unsynchronized 1.2 Collection classes because we were still committed to running on Java 1.1.8. Now that Xerces has given up compatabi

Performance problem for Xalan-J on intel-dual core

Over the last week I've been working with Toadie (a Xalan user) who had some very serious performance degradation with a webserver using Xalan. On an intel dual-core machine it was 10 times slowdown than for a single processor intel machine. The problem occurs in this combination for the l

[jira] Resolved: (XALANJ-2295) XSLTC performance problems with xsl:key in Muenchian grouping

[ http://issues.apache.org/jira/browse/XALANJ-2295?page=all ] Henry Zongaro resolved XALANJ-2295: --- Fix Version: Latest Development Code Resolution: Fixed Applied patch in source repository. > XSLTC performance problems with xsl:key

[jira] Commented: (XALANJ-2295) XSLTC performance problems with xsl:key in Muenchian grouping

[ http://issues.apache.org/jira/browse/XALANJ-2295?page=comments#action_12415180 ] Christine Li commented on XALANJ-2295: -- The patch looks good and it resolves the problems described by XALANJ-2292, XALANJ-2294 and XALANJ2295. > XSLTC performa

[jira] Created: (XALANJ-2295) XSLTC performance problems with xsl:key in Muenchian grouping

XSLTC performance problems with xsl:key in Muenchian grouping - Key: XALANJ-2295 URL: http://issues.apache.org/jira/browse/XALANJ-2295 Project: XalanJ2 Type: Bug Components: XSLTC Versions: 2.7

[jira] Closed: (XALANC-593) Poor performance with a complex XSL stylesheet and large XML file

[ http://issues.apache.org/jira/browse/XALANC-593?page=all ] David Bertoni closed XALANC-593: Resolution: Won't Fix > Poor performance with a complex XSL stylesheet and large

Re: How to improve the XPath query performance

Tel: (905)413-2601 Email: [EMAIL PROTECTED] "Weijian Fang" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 03/14/2006 05:33 AM Please respond to xalan-dev@xml.apache.org To xalan-dev@xml.apache.org cc Subject How to improve the XPath query performance

How to improve the XPath query performance

Hi, I am using Xalan's XPath Java API. I have some questions related to its query performance. 1. Given a dom tree, are there some general methods to improve the XPath query performance, such as indexing, etc.? It is very kind if you can direct me to some links, docs, or Java classes.

DO NOT REPLY [Bug 7294] - Performance Issue - CachedXPathAPI

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug

[jira] Commented: (XALANC-593) Poor performance with a complex XSL stylesheet and large XML file

is the performane is not really optimal. > Poor performance with a complex XSL stylesheet and large XML file > - > > Key: XALANC-593 > URL: http://issues.apache.org/jira/browse/XALANC-593 >

[jira] Commented: (XALANC-593) Poor performance with a complex XSL stylesheet and large XML file

iseconds. Stylesheet compilation time: 68.1234694 milliseconds. Transformation time: 55857.444942 milliseconds. === > Poor performance with a complex XSL stylesheet and large XML file > - > >

[jira] Created: (XALANC-593) Poor performance with a complex XSL stylesheet and large XML file

Poor performance with a complex XSL stylesheet and large XML file - Key: XALANC-593 URL: http://issues.apache.org/jira/browse/XALANC-593 Project: XalanC Type: Bug Components: XalanC Versions

[jira] Closed: (XALANC-556) Major performance issue

[ http://issues.apache.org/jira/browse/XALANC-556?page=all ] David Bertoni closed XALANC-556: > Major performance issue > --- > > Key: XALANC-556 > URL: http://issues.apache.org/jira/br

[jira] Resolved: (XALANC-556) Major performance issue

[ http://issues.apache.org/jira/browse/XALANC-556?page=all ] David Bertoni resolved XALANC-556: -- Fix Version: CurrentCVS Resolution: Fixed This is a duplicate of XALANC-539. > Major performance is

[jira] Created: (XALANC-556) Major performance issue

Major performance issue --- Key: XALANC-556 URL: http://issues.apache.org/jira/browse/XALANC-556 Project: XalanC Type: Bug Components: XalanC Versions: 1.9 Reporter: Yves Monier I recently switched from xalan-c 1.4 (with xerces-c

[jira] Closed: (XALANJ-2089) Performance degradation in ElemNumber.

[ http://issues.apache.org/jira/browse/XALANJ-2089?page=all ] Brian Minchau closed XALANJ-2089: - Yash, I've taken the liberty of closing this issue for you. Re-open if you need to, but I sure hope you don't do that. > Performance d

[jira] Closed: (XALANJ-1700) Performance regression for HTML output with tabs in attributes

[ http://issues.apache.org/jira/browse/XALANJ-1700?page=all ] Brian Minchau closed XALANJ-1700: - Assign To: (was: Xalan Developers Mailing List) > Performance regression for HTML output with tabs in attribu

[jira] Updated: (XALANJ-1689) redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares

[ http://issues.apache.org/jira/browse/XALANJ-1689?page=all ] Brian Minchau updated XALANJ-1689: -- Version: 2.5Dx (was: Latest Development Code) > redirect uses unbuffered FileOutputStream -> bad performance when accessing >

[jira] Updated: (XALANJ-1194) Performance Query

[ http://issues.apache.org/jira/browse/XALANJ-1194?page=all ] Brian Minchau updated XALANJ-1194: -- Version: 2.4Dx (was: Latest Development Code) > Performance Query > - > > Key: XALANJ-1194 >

[jira] Updated: (XALANJ-1905) xslt multithreaded performance

[ http://issues.apache.org/jira/browse/XALANJ-1905?page=all ] Brian Minchau updated XALANJ-1905: -- Version: 2.6 (was: Latest Development Code) > xslt multithreaded performance > -- > >

[jira] Updated: (XALANJ-1905) xslt multithreaded performance

[ http://issues.apache.org/jira/browse/XALANJ-1905?page=all ] Brian Minchau updated XALANJ-1905: -- Version: Latest Development Code (was: 2.6) > xslt multithreaded performance > -- > >

[jira] Updated: (XALANJ-1194) Performance Query

[ http://issues.apache.org/jira/browse/XALANJ-1194?page=all ] Brian Minchau updated XALANJ-1194: -- Version: Latest Development Code (was: 2.4Dx) > Performance Query > - > > Key: XALANJ-1194 >

[jira] Updated: (XALANJ-1689) redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares

[ http://issues.apache.org/jira/browse/XALANJ-1689?page=all ] Brian Minchau updated XALANJ-1689: -- Version: Latest Development Code (was: 2.5Dx) > redirect uses unbuffered FileOutputStream -> bad performance when accessing >

[jira] Updated: (XALANJ-1907) Performance degradation for xsl:copy and xsl:copy-of

[ http://issues.apache.org/jira/browse/XALANJ-1907?page=all ] Brian Minchau updated XALANJ-1907: -- Fix Version: 2.7 > Performance degradation for xsl:copy and xsl:copy-of > > >

[jira] Updated: (XALANJ-2089) Performance degradation in ElemNumber.

[ http://issues.apache.org/jira/browse/XALANJ-2089?page=all ] Brian Minchau updated XALANJ-2089: -- Fix Version: 2.7 (was: CurrentCVS) > Performance degradation in ElemNumber. > -- > >

[jira] Resolved: (XALANJ-1560) Performance Problems-NEED HELP!

lving as "Won't Fix". Significant performance work has gone in since 2.4.0, but not enough for issue reporter. The testcase provided by Andreas Felix may yet be useful in the future. However we no longer consider this issue active. > Perform

[jira] Resolved: (XALANJ-2089) Performance degradation in ElemNumber.

[ http://issues.apache.org/jira/browse/XALANJ-2089?page=history ] Yash Talwar resolved XALANJ-2089: - Resolution: Fixed Fix Version: CurrentCVS Patch commited to CVS. > Performance degradation in ElemNum

[jira] Updated: (XALANJ-2089) Performance degradation in ElemNumber.

[ http://issues.apache.org/jira/browse/XALANJ-2089?page=history ] Brian Minchau updated XALANJ-2089: -- reviewer: [EMAIL PROTECTED] > Performance degradation in ElemNumber. > -- > > Key:

[jira] Commented: (XALANJ-2089) Performance degradation in ElemNumber.

Class static variable. So its scope is the one XSL transformation. The old static variable caching was cached for all transactions in the same JVM, which has implications in a server environment. As an instance field it is safe. I have reviewed and approve the patch. > Performance degradat

[jira] Updated: (XALANJ-2089) Performance degradation in ElemNumber.

[ http://issues.apache.org/jira/browse/XALANJ-2089?page=history ] Yash Talwar updated XALANJ-2089: Xalan info: [PatchAvailable] > Performance degradation in ElemNumber. > -- > > Key:

[jira] Updated: (XALANJ-2089) Performance degradation in ElemNumber.

dynamic change. To resolve this defect and another potential security bug, Christine Li had changed the code to obtain the resource bundle for every request. This had resulted in bad performance. The performance hit was seen during a performance testing phase. I found the source of the problem

[jira] Created: (XALANJ-2089) Performance degradation in ElemNumber.

Performance degradation in ElemNumber. -- Key: XALANJ-2089 URL: http://issues.apache.org/jira/browse/XALANJ-2089 Project: XalanJ2 Type: Bug Environment: Windows 2000 Reporter: Yash Talwar Assigned to: Yash Talwar

Re: Performance implications of factory model in Xalan?

Hi, Rick. "Rick Bullotta" <[EMAIL PROTECTED]> wrote on 2004-12-28 07:42:56 AM: > Yes, I know this is a loaded question , but we've found that factory > models are often causing SIGNIFICANT performance hits on object creation, > especially when the factory has to

RE: Performance implications of factory model in Xalan?

org.apache.xerces.jaxp.SAXParserFactoryImpl"); } These affect performance a lot of things, notably obtaining DocumentBuilders, Transformers, and XPathContexts (and indirectly, CachedXPathAPI objects and XPathAPI static method performance). We're talking about an order of mag

Performance implications of factory model in Xalan?

Yes, I know this is a loaded question , but we've found that factory models are often causing SIGNIFICANT performance hits on object creation, especially when the factory has to defer to looking for property files, getResourceAsStream(), and the classloader's handling of class.for

[jira] Updated: (XALANJ-1194) Performance Query

[ http://nagoya.apache.org/jira/browse/XALANJ-1194?page=history ] Henry Zongaro updated XALANJ-1194: -- Priority: Major > Performance Query > - > > Key: XALANJ-1194 > URL: http://nagoya.apache.org/jira/bro

[jira] Updated: (XALANJ-1905) xslt multithreaded performance

[ http://nagoya.apache.org/jira/browse/XALANJ-1905?page=history ] Henry Zongaro updated XALANJ-1905: -- Priority: Major > xslt multithreaded performance > -- > > Key: XALANJ-1905 >

[jira] Updated: (XALANJ-1689) redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares

[ http://nagoya.apache.org/jira/browse/XALANJ-1689?page=history ] Henry Zongaro updated XALANJ-1689: -- Priority: Major > redirect uses unbuffered FileOutputStream -> bad performance when accessing > networked Windo

[jira] Updated: (XALANJ-1474) XSLTC: performance improvement for stepPattern[last()]

[ http://nagoya.apache.org/jira/browse/XALANJ-1474?page=history ] Henry Zongaro updated XALANJ-1474: -- Assign To: (was: Xalan Developers Mailing List) type: Improvement (was: Bug) Description: A todo item for future performance

[jira] Updated: (XALANJ-984) Performance Enhancement to Xalan distinct function

within the method, there really is not need to use an object that synchronizes access to its instance. To improve performance, a HashSet should be used. Furthermore, it is a good idea to manually clear the HashSet at the end of the method to ensure the HashSet instance is garbage collected. The

[jira] Updated: (XALANJ-1296) Performance problem due to unnecessary ArrayIndexOutOfBoundsException

DTMManagerDefault.getDTM() checks for a DTM.NULL argument *after* catching an ArrayIndexOutOfBoundsException instead of *before*. The in- line comment indicates this function is performance critical. OptimizeIt indicates that the performance of the current implementation suffers because of the unnecessary

[jira] Updated: (XALANJ-1229) Performance problem with Xalan 2.0 -> 2.4

large performance problem with my application. My application : I use domify (http://domify.sourceforge.net/) to build a DOM tree from a JavaBean hierarchy. The DOM tree is build 'lazy'. That is : Only when the elements are needed they are created. The hierary is as follows: Regist

[jira] Updated: (XALANJ-917) Performance Issue - CachedXPathAPI

essor methods to the CachedXPathAPI object: public ErrorHandler getErrorHandler(); public void setErrorHandler(ErrorHandler errorHandler); Thanks, Aaron Environment: Operating System: All Platform: All was: Operating System: All Platform: All Priority: Major Bugzilla Id: (was:

[jira] Updated: (XALANJ-1560) Performance Problems-NEED HELP!

[ http://nagoya.apache.org/jira/browse/XALANJ-1560?page=history ] Henry Zongaro updated XALANJ-1560: -- Priority: Critical > Performance Problems-NEED HELP! > --- > > Key: XALANJ-1560 >

[jira] Updated: (XALANJ-1372) Performance improvement ideas wrt loading JAXP Factories and DTMManager

[ http://nagoya.apache.org/jira/browse/XALANJ-1372?page=history ] Henry Zongaro updated XALANJ-1372: -- Priority: Major (was: Blocker) > Performance improvement ideas wrt loading JAXP Factories and DTMMana

[jira] Updated: (XALANJ-1229) Performance problem with Xalan 2.0 -> 2.4

: - Key: XALANJ-1229 Summary: Performance problem with Xalan 2.0 -> 2.4 Type: Bug Status: Open Project: XalanJ2 Components: Xalan-interpretive transformation transformation Versions: 2.4 Assignee: Xa

[jira] Updated: (XALANJ-1905) xslt multithreaded performance

: - Key: XALANJ-1905 Summary: xslt multithreaded performance Type: Bug Status: Open Project: XalanJ2 Components: Xalan-interpretive transformation transformation Versions: 2.6 Assignee: Xalan Developers Mailing

[jira] Updated: (XALANJ-19) Request for performance enhancement to contains() function

: - Key: XALANJ-19 Summary: Request for performance enhancement to contains() function Type: Improvement Status: Unassigned Priority: Minor Project: XalanJ2 Components: XPath function

[jira] Updated: (XALANJ-19) Request for performance enhancement to contains() function

--- View the issue: http://issues.apache.org/jira/browse/XALANJ-19 Here is an overview of the issue: ----- Key: XALANJ-19 Summary: Request for performance enhancement to contains() function Type: Bug Statu

[jira] Updated: (XALANJ-1372) Performance improvement ideas wrt loading JAXP Factories and DTMManager

iew of the issue: - Key: XALANJ-1372 Summary: Performance improvement ideas wrt loading JAXP Factories and DTMManager Type: Bug Status: Unassigned Priority: Blocker Project: XalanJ2

DO NOT REPLY [Bug 30056] - Performance degradation for xsl:copy and xsl:copy-of

gzilla/show_bug.cgi?id=30056 Performance degradation for xsl:copy and xsl:copy-of [EMAIL PROTECTED] changed: What|Removed |Added AssignedTo|[EMAIL PROTECTED]|[EMAIL PRO

DO NOT REPLY [Bug 30056] - Performance degradation for xsl:copy and xsl:copy-of

gzilla/show_bug.cgi?id=30056 Performance degradation for xsl:copy and xsl:copy-of --- Additional Comments From [EMAIL PROTECTED] 2004-07-12 19:07 --- Performance degradation was introduced in fix for bug 22808. - To unsub

DO NOT REPLY [Bug 29980] - xslt multithreaded performance

gzilla/show_bug.cgi?id=29980 xslt multithreaded performance [EMAIL PROTECTED] changed: What|Removed |Added Priority|Other |

DO NOT REPLY [Bug 30056] - Performance degradation for xsl:copy and xsl:copy-of

gzilla/show_bug.cgi?id=30056 Performance degradation for xsl:copy and xsl:copy-of [EMAIL PROTECTED] changed: What|Removed |Added Priority|Other

DO NOT REPLY [Bug 30056] - Performance degradation for xsl:copy and xsl:copy-of

gzilla/show_bug.cgi?id=30056 Performance degradation for xsl:copy and xsl:copy-of --- Additional Comments From [EMAIL PROTECTED] 2004-07-12 16:49 --- Created an attachment (id=12095) Input document that demonstrates the performance p

DO NOT REPLY [Bug 30056] - Performance degradation for xsl:copy and xsl:copy-of

gzilla/show_bug.cgi?id=30056 Performance degradation for xsl:copy and xsl:copy-of --- Additional Comments From [EMAIL PROTECTED] 2004-07-12 16:49 --- Created an attachment (id=12094) Stylesheet that demonstrates the performance p

DO NOT REPLY [Bug 30056] New: - Performance degradation for xsl:copy and xsl:copy-of

gzilla/show_bug.cgi?id=30056 Performance degradation for xsl:copy and xsl:copy-of Summary: Performance degradation for xsl:copy and xsl:copy-of Product: XalanJ2 Version: 2.6 Platform: All OS/Version: All Status: NEW Severity:

DO NOT REPLY [Bug 29980] New: - xslt multithreaded performance

gzilla/show_bug.cgi?id=29980 xslt multithreaded performance Summary: xslt multithreaded performance Product: XalanJ2 Version: 2.6 Platform: PC OS/Version: Linux Status: NEW Severity: Normal Priority: Other Com

DO NOT REPLY [Bug 23863] - redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares

gzilla/show_bug.cgi?id=23863 redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares --- Additional Comments From [EMAIL PROTECTED] 2004-05-31 18:01 --- The BufferedOutputStream looks like a good idea, but it would probably need to keep a

DO NOT REPLY [Bug 23863] - redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares

gzilla/show_bug.cgi?id=23863 redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares [EMAIL PROTECTED] changed: What|Removed |Added

DO NOT REPLY [Bug 24025] - Performance regression for HTML output with tabs in attributes

gzilla/show_bug.cgi?id=24025 Performance regression for HTML output with tabs in attributes --- Additional Comments From [EMAIL PROTECTED] 2003-11-05 14:55 --- This bug has been fixed in Xalan Java 2.5.2. Please verify.

DO NOT REPLY [Bug 24025] - Performance regression for HTML output with tabs in attributes

gzilla/show_bug.cgi?id=24025 Performance regression for HTML output with tabs in attributes [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 24025] - Performance regression for HTML output with tabs in attributes

gzilla/show_bug.cgi?id=24025 Performance regression for HTML output with tabs in attributes [EMAIL PROTECTED] changed: What|Removed |Added Ke

DO NOT REPLY [Bug 24025] - Performance regression for HTML output with tabs in attributes

gzilla/show_bug.cgi?id=24025 Performance regression for HTML output with tabs in attributes --- Additional Comments From [EMAIL PROTECTED] 2003-10-23 00:44 --- Created an attachment (id=8683) Patch to CharInfo in serializer to make it smarter/faster

DO NOT REPLY [Bug 24025] New: - Performance regression for HTML output with tabs in attributes

gzilla/show_bug.cgi?id=24025 Performance regression for HTML output with tabs in attributes Summary: Performance regression for HTML output with tabs in attributes Product: XalanJ2 Version: CurrentCVS Platform: Other OS/Version:

DO NOT REPLY [Bug 23863] - redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares

gzilla/show_bug.cgi?id=23863 redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares --- Additional Comments From [EMAIL PROTECTED] 2003-10-16 13:07 --- Hmmm. We've had preformance problems in the past caused by _excessive_ buffer

DO NOT REPLY [Bug 23863] New: - redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares

gzilla/show_bug.cgi?id=23863 redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares Summary: redirect uses unbuffered FileOutputStream -> bad performance when accessing networked Windows Shares Prod

DO NOT REPLY [Bug 19900] - Minor performance fixes to the serializer

gzilla/show_bug.cgi?id=19900 Minor performance fixes to the serializer [EMAIL PROTECTED] changed: What|Removed |Added Status|RESOLVED|CLOSED --- Addi

DO NOT REPLY [Bug 19474] - Performance: Serializer buffers Outupt when its output is to BufferedServletOutputStream

gzilla/show_bug.cgi?id=19474 Performance: Serializer buffers Outupt when its output is to BufferedServletOutputStream [EMAIL PROTECTED] changed: What|Removed |Added Status|VE

DO NOT REPLY [Bug 19474] - Performance: Serializer buffers Outupt when its output is to BufferedServletOutputStream

gzilla/show_bug.cgi?id=19474 Performance: Serializer buffers Outupt when its output is to BufferedServletOutputStream [EMAIL PROTECTED] changed: What|Removed |Added Status|RE

DO NOT REPLY [Bug 20710] - Performance Problems-NEED HELP!

gzilla/show_bug.cgi?id=20710 Performance Problems-NEED HELP! --- Additional Comments From [EMAIL PROTECTED] 2003-08-14 06:58 --- hello Brian! sorry of my spare answers in the last time. we tested some other XSLT´s with our application and decided to change to an another product. XALAN is t

DO NOT REPLY [Bug 20710] - Performance Problems-NEED HELP!

gzilla/show_bug.cgi?id=20710 Performance Problems-NEED HELP! --- Additional Comments From [EMAIL PROTECTED] 2003-08-13 21:37 --- Hi Andreas, we've looked at your sample in some detail and run it with various performance tools. I've seen that much of the time is in the "stac

DO NOT REPLY [Bug 20710] - Performance Problems-NEED HELP!

gzilla/show_bug.cgi?id=20710 Performance Problems-NEED HELP! --- Additional Comments From [EMAIL PROTECTED] 2003-07-11 19:43 --- First, my performance analysis is only for XSLTC. For XSLTC, half of the execution time is spent in the evaluation of global variables (there are many global v

DO NOT REPLY [Bug 20710] - Performance Problems-NEED HELP!

gzilla/show_bug.cgi?id=20710 Performance Problems-NEED HELP! --- Additional Comments From [EMAIL PROTECTED] 2003-07-11 19:39 --- I don't know if it is because of the fix for bug 21491, but XSLTC now runs about 15% faster (not slower) than Xalan-J interpretive for the example th

DO NOT REPLY [Bug 20710] - Performance Problems-NEED HELP!

gzilla/show_bug.cgi?id=20710 Performance Problems-NEED HELP! --- Additional Comments From [EMAIL PROTECTED] 2003-07-11 07:28 --- With the fix for bug 21491 the class WriterToUTF8Buffered does not slow down for very large input of character arrays or Strings. I had tried writing out a

DO NOT REPLY [Bug 20710] - Performance Problems-NEED HELP!

gzilla/show_bug.cgi?id=20710 Performance Problems-NEED HELP! --- Additional Comments From [EMAIL PROTECTED] 2003-07-10 21:55 --- Andreas, in the profiling that I did the majority of the time was related to template processing. I thought of one way to reduce the number of template stack

DO NOT REPLY [Bug 20710] - Performance Problems-NEED HELP!

gzilla/show_bug.cgi?id=20710 Performance Problems-NEED HELP! --- Additional Comments From [EMAIL PROTECTED] 2003-07-10 18:40 --- Several advices 1. Try to use XSLTC setting ( before creating TransformerFactory) System.setProperty("javax.xml.transform.Transfo

DO NOT REPLY [Bug 20710] - Performance Problems-NEED HELP!

gzilla/show_bug.cgi?id=20710 Performance Problems-NEED HELP! [EMAIL PROTECTED] changed: What|Removed |Added Priority|Other |Medium

DO NOT REPLY [Bug 20710] - Performance Problems-NEED HELP!

gzilla/show_bug.cgi?id=20710 Performance Problems-NEED HELP! --- Additional Comments From [EMAIL PROTECTED] 2003-06-23 07:52 --- Sorry, for the late answer. We tested some other XSLT´s with our application. in the zip file, i sent you testdata. explaination: sp_1.xml is the Input- Sour

DO NOT REPLY [Bug 20710] - Performance Problems-NEED HELP!

gzilla/show_bug.cgi?id=20710 Performance Problems-NEED HELP! --- Additional Comments From [EMAIL PROTECTED] 2003-06-23 07:49 --- Created an attachment (id=6935) Testdata (XML + XSL´s)

  1   2   3   >