Return-Path: Delivered-To: apmail-xml-general-archive@xml.apache.org Received: (qmail 11844 invoked by uid 500); 15 Mar 2001 23:09:40 -0000 Mailing-List: contact general-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: general@xml.apache.org Delivered-To: mailing list general@xml.apache.org Received: (qmail 11793 invoked from network); 15 Mar 2001 23:09:38 -0000 X-Originating-IP: [63.206.124.79] From: "Lyle Coder" To: Subject: Xerces multithreaded performance Date: Thu, 15 Mar 2001 15:10:30 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Message-ID: X-OriginalArrivalTime: 15 Mar 2001 23:09:16.0211 (UTC) FILETIME=[F4F1E830:01C0ADA4] X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N Hi, I am using the Xerces DOM API. When I am creating DOMs simultaneously via different threads, I have a serious performance bottle neck. Many times, my application just STALLS and I use GDB to break in and see where the stall is and it is ALWAYS in Xerces where I am calling some Xerces allocation function like XercesElement->createElement() I mean... I get better performance with just one thread. And if you are wondering, my code does not hold any locks at all (no semaphores), so I know it is not my program thats the bottle neck So the question is, has any one else seen this, and if so, do you have a solution Thanks Lyle --------------------------------------------------------------------- In case of troubles, e-mail: webmaster@xml.apache.org To unsubscribe, e-mail: general-unsubscribe@xml.apache.org For additional commands, e-mail: general-help@xml.apache.org