Hi,<br><br>There are two things to note here:<br>a) the ESV is a compressed module (uses the zText driver). <br>The zText driver is quite a bit slower than the rawtext one (around 20-30x slower!)<br>Here are the times taken to getRawEntry for a compressed and uncompressed ESV:<br>
uncompressed: 1.89 seconds (this is a good length of time)<br>compressed: 40.461 seconds (this isn't)<br><br>This is a tad depressing - especially since all new modules seem to be being compressed.<br><br>b) the osishtmlhref filter is quite slow. <br>
It took 72 seconds to render the text got above. The plain filter took 10 seconds.<br><br>Also, just because a tag is stored inline doesn't mean its faster to leave it on. If it is turned off, the tag will be stripped out, which should be a good deal quicker than processing it.<br>
<br clear="all">God Bless,<br>Ben<br>-------------------------------------------------------------------------------------------<br>The Lord is not slow to fulfill his promise as some count slowness,<br>but is patient toward you, not wishing that any should perish,<br>
but that all should reach repentance.<br>2 Peter 3:9 (ESV)
<br><br><div class="gmail_quote">On Tue, Jul 8, 2008 at 12:39 AM, Troy A. Griffitts <<a href="mailto:scribe@crosswire.org">scribe@crosswire.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
David,<br>
<br>
You of all people should know this... :) SWORD stores all the tags<br>
inline in the text. When you start turning things OFF is when all the<br>
filters have to do work to remove things. If everything is left on,<br>
then the text is just handed back as it was stored. I'm still not<br>
convinced. :)<br>
<font color="#888888"><br>
-Troy.<br>
</font><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
David Trotz wrote:<br>
> Troy,<br>
>> Just a note regarding the comment that the SWORD engine take > 6 seconds<br>
>> to render psalm119...<br>
>><br>
>> If this is the case there is a bug somewhere.<br>
>><br>
> Perhaps there is a bug, because...<br>
>> It usually takes < 6 seconds to render an entire Bible to a file on a<br>
>> low end PC, which I'm guessing is about the same power as todays handhelds.<br>
>><br>
>> My guess is that the extreme amount of tags in the text is taking the<br>
>> HTML renderer the time.<br>
>><br>
> ... it takes my HTML renderer very little time (1s for Psalm 119 w/ full<br>
> markup in ESV) to render any given text. I have tested this by<br>
> preloading text from a file then shoving it into the HTML renderer. But<br>
> as soon as we start to query sword for text from a module we take a<br>
> significant performance hit. Its only if I turn off all the extra<br>
> features in the text such as strong's numbers or footnotes in ESV that<br>
> things are very fast. Perhaps you can look at how we are pulling text<br>
> from sword and see if there is something wrong with our methodology?<br>
>> Just trying to pass the buck until someone PROVES to me that we need<br>
>> optimization in the engine. :)<br>
>><br>
> I understand that all too well. ;-)<br>
><br>
> BTW have you given it a run on your new smartphone?<br>
><br>
> In Christ,<br>
> David Trotz<br>
><br>
> _______________________________________________<br>
> sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
> <a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
> Instructions to unsubscribe/change your settings at above page<br>
<br>
<br>
_______________________________________________<br>
sword-devel mailing list: <a href="mailto:sword-devel@crosswire.org">sword-devel@crosswire.org</a><br>
<a href="http://www.crosswire.org/mailman/listinfo/sword-devel" target="_blank">http://www.crosswire.org/mailman/listinfo/sword-devel</a><br>
Instructions to unsubscribe/change your settings at above page<br>
</div></div></blockquote></div><br>