[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: What should TrAX look like? (Was: Re: Article on

• To: Elliotte Harold <elharo@m...>
• Subject: Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
• From: Wolfgang Hoschek <whoschek@l...>
• Date: Wed, 23 Feb 2005 12:24:45 -0800
• Cc: kjouk@y..., xml-dev@l...
• In-reply-to: <421CE54B.2060507@m...>
• References: <E1D2Si4-0001QA-00@u...> <200502211623.51418.kjones@s...> <421A0ECF.3090802@m...> <200502220742.53890.kjouk@y...> <421B03D2.6020803@m...> <e3e82eebdc6fa9346729066b1497431b@l...> <421C8024.9010505@m...> <d091208de21a45d5dc1d820d8806e122@l...> <421CE54B.2060507@m...>

On Feb 23, 2005, at 12:19 PM, Elliotte Harold wrote:

> Wolfgang Hoschek wrote:
>
>> Just run pretty much any query over more than toy data, say 1 - 100 
>> MB instead of 1 KB.
>> For example, simply run a benchmark driver such as
>> java -server nux.xom.tests.XQueryBenchmark 1000 3 xom 
>> samples/data/randj.xml samples/xpath/queries1.xml
>> The only reason I didn't publish the results for XOM's Jaxen XPath is 
>> because I considered them too embarrassing for you. It really escapes 
>> me why you are asking for it. Shall I really attach the catastrophic 
>> numbers to this mail?
>
> Feel free to attach any numbers you want, but numbers that don't come 
> with verifiable, testable data are pretty much meaningless. Again I 
> ask, if you have a real test case send it to me or send it the 
> xom-interest mailing list, and I can look at it. But without the 
> actual raw data that's used to generate the numbers, it's all just hot 
> air.
>

Download Nux and run the command given above. Data and queries are part 
of the download. That's it, and you know it. No need to act like being 
deaf.

Wolfgang.

• Follow-Ups:
  • Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
    • From: Elliotte Harold <elharo@m...>

• References:
  • RE: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: "Michael Kay" <mike@s...>
  • Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: Kevin Jones <kjones@s...>
  • Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
    • From: Elliotte Harold <elharo@m...>
  • Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
    • From: Elliotte Harold <elharo@m...>
  • Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: Wolfgang Hoschek <whoschek@l...>
  • Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
    • From: Elliotte Harold <elharo@m...>
  • Re: What should TrAX look like? (Was: Re: Article on JAXP 1.3 "Fast and Easy XML Processing")
    • From: Wolfgang Hoschek <whoschek@l...>
  • Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
    • From: Elliotte Harold <elharo@m...>

• Prev by Date: Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
• Next by Date: Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
• Previous by thread: Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
• Next by thread: Re: What should TrAX look like? (Was: Re: Articleon JAXP 1.3 "Fast and Easy XML Processing")
• Index(es):
  • Date
  • Thread