Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] Cache misses in namespace URI verification

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: Wolfgang Hoschek <whoschek AT lbl.gov>
  • To: Elliotte Harold <elharo AT metalab.unc.edu>
  • Cc: xom-interest <xom-interest AT lists.ibiblio.org>
  • Subject: Re: [XOM-interest] Cache misses in namespace URI verification
  • Date: Fri, 10 Dec 2004 12:15:46 -0800

On Dec 10, 2004, at 12:03 PM, Elliotte Harold wrote:

Wolfgang Hoschek wrote:


Each call to builder.build(...) produces another 5 misses, so it seems xerces does not keep the URIs interned across builds. But that's fine and no problem.

If it doesn't keep the URIs interned across builds, then how does that affect multithreaded environments where you could be building from several documents at once?

Because everything in nu.xom.Verifier is static. All threads are contending for the same shared lock in the URICache, irrespective of whether they work in the same or different documents. If you have 100 threads, each rapidly executing URICache.contains() millions of times you can get a lot of lock contention and serious performance degradation.

Wolfgang.





Archive powered by MHonArc 2.6.24.

Top of Page