Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Exploiting multi-core CPUs during XML parsing

From: Sean McGrath <sean.mcgrath@--------.--->
To: xml-dev@-----.---.---
Date: 4/1/2006 7:20:00 AM
I have sketched out an algorithm for fast XML WF parsing utilising two 
threads that each start at opposite ends of the octet-stream and meet in 
the middle. The algorithm hinges on the fact that start- and end-tags 
are balanced. i.e. as one thread reads forward looking for foo 
start-tag, the other thread is reading backwards looking for foo end-tag.

This also has the nice side effect of giving you accurate error messages 
quickly. i.e. as soon as a mismatched tag is found, it can be reported. 
This is particularly useful with recursive element types.

Modern machines (even desktop boxes) will increasingly have multi-core 
CPUs as standard and I think it behooves us to find ways of exploiting 
that in the XML world.

But to get the most out of the algorithm, you really need a filesystem 
that supports reading byte-streams backwards.

Does anyone know of such a filesystem?

thanks,
Sean


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent