<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style="font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 10pt;"><div>Hi folks,<br></div><div><br></div><div><br></div><div>Thanks to all who helped, it looks like the Squeak/Spur64 will be faster than the pharo. It is currently at (120 Million elements parsed in ~33 minutes).<br></div><div><br></div><div>woot!<br></div><div><br></div><div><br></div><div>The next step is an architecture plan/ brainstorming.<br></div><div><br></div><div><br></div><div>What I am thinking is to take the components of the SAX Parse and wrap them in a Squeak object containing the contents and meta-information.<br></div><div><br></div><div>I then want to make those objects available to other instances of Squeak hosting Xtreams-Parsing where the contents can be parsed and converted to different formats: xHTML to start.<br></div><div><br></div><div>If <a target="_blank" href="http://www.squeaksource.com/AMQP/">http://www.squeaksource.com/AMQP/</a> AMQP can handle "objects" then I can use STOMP (which I used before, about 10 years ago for a commercial app involving squeak)<br></div><div><br></div><div>so...SAX(Wrap)->Wrap->AMQP(Competing consumers model) <a target="_blank" href="https://www.enterpriseintegrationpatterns.com/patterns/messaging/CompetingConsumers.html">https://www.enterpriseintegrationpatterns.com/patterns/messaging/CompetingConsumers.html</a>) ->* "many squeaks(Xtreams-Parsing).<br></div><div><br></div><div>And, per the "75 Gb discussion" store those things in multiple nodes according to some internal logic.<br></div><div><br></div><div>Sound reasonable?<br></div><div><br></div><div>cheers,<br></div><div><br></div><div>tty</div></div><br></body></html>