xml-xindice-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "webhiker@tiscali.fr" <webhi...@tiscali.fr>
Subject Re: teamup for the great ideas (xindice pros & cons)
Date Mon, 20 Oct 2003 07:28:12 GMT
Whatever you feel comfortable doing.
I've identified the following main tasks that need completing :
1)Writing a custom xslt to replace the Ant JUnitReport task, so that 
test results will be automatically generated in a format easier
to compare iwth runs against different DB's
2)Writing more tests - Level 0 and Level 1 tests (as per XML:DB)


WH

chasee wrote:

> what is the first step of the help?
>
> */"webhiker@tiscali.fr" <webhiker@tiscali.fr>/* wrote:
>
>     Just to update, I've started a project on Sourceforge
>     http://xmldbench.sourceforge.net
>     I'm still setting up the workspace, build files, layout etc, so
>     there's
>     not much to see.
>     However this is a call for help for anyone who's interested in
>     helping
>     out with this project.
>     Especially helpfull will be anyone familiar with the workings of
>     JUnit.
>     Drop me a note if you're interested.
>
>     Cheers.
>     WH
>
>     chasee wrote:
>
>     > To all:
>     >
>     > it's nice that this topic finally leads to a "theoretical and
>     > experimental analysis of current xml db technology" type of thing.
>     >
>     > I have summarize the great ideas you guys have proposed for the
>     > analysis and added in my own understanding and thoughts. Indeed it
>     > seems something that could contribute to the maturity of the xml db
>     > technology, if the we have more theoretical stuff stuck in.
>     Shall we
>     > team up for a research topic if not enough for a project as steve
>     > suggested? Send email to me or steve if you vote for this idea...
>     >
>     > ** "theoretical and experimental analysis of current xml db
>     technology"**
>     >
>     > Z)Theoretical comparison
>     > 1* index structure and indexing behavior
>     > 2* memeory leaking handling
>     > 3* recovery strategy
>     > 4* XUpdate semantics
>     >
>     >
>     > A) XML:DB tests ---------------
>     > 1* access times for adding documents graphed against total
>     resource count
>     > 2* access times for deleting documents graphed against total
>     resource
>     > count
>     > 3* access times for updating documents graphed against total
>     resource
>     > count
>     >
>     >
>     > B) XML:DB:XPATH tests ------------------------
>     > 1* access times for querying documents graphed against total
>     resource
>     > count -for single document match -for multiple document match
>     > 2* perform more and more general query to find the maximum
>     ResourceSet
>     > size which can be managed
>     >
>     >
>     > C) Stress & Robustness tests --------------------------
>     > 1* repeatedly add a single smallish document with different id
>     to get
>     > max resource count possible within a collection
>     > 2* update a single document repeatedly, while increasing it's
>     size, to
>     > get max single resource size
>     > 3. increasing the collection size with a constant load util the
>     > instability of the db is observed.
>     >
>     >
>     >
>     > ============
>     > thanks,
>     > chasee
>     >
>     ------------------------------------------------------------------------
>     > Do you Yahoo!?
>     > The New Yahoo! Shopping
>     >
>     > - with improved product search
>
>
>
>
> ============
> thanks,
> chasee
> ------------------------------------------------------------------------
> Do you Yahoo!?
> The New Yahoo! Shopping 
> <http://shopping.yahoo.com/?__yltc=s%3A150000443%2Cd%3A22708228%2Cslk%3Atext%2Csec%3Amail>

> - with improved product search 




Mime
View raw message