[sword-devel] SwordReader PocketPC and SmartPhone CAB files.
benpmorgan at gmail.com
Tue Jul 8 06:46:41 MST 2008
There are two things to note here:
a) the ESV is a compressed module (uses the zText driver).
The zText driver is quite a bit slower than the rawtext one (around 20-30x
Here are the times taken to getRawEntry for a compressed and uncompressed
uncompressed: 1.89 seconds (this is a good length of time)
compressed: 40.461 seconds (this isn't)
This is a tad depressing - especially since all new modules seem to be being
b) the osishtmlhref filter is quite slow.
It took 72 seconds to render the text got above. The plain filter took 10
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.
The Lord is not slow to fulfill his promise as some count slowness,
but is patient toward you, not wishing that any should perish,
but that all should reach repentance.
2 Peter 3:9 (ESV)
On Tue, Jul 8, 2008 at 12:39 AM, Troy A. Griffitts <scribe at crosswire.org>
> You of all people should know this... :) SWORD stores all the tags
> inline in the text. When you start turning things OFF is when all the
> filters have to do work to remove things. If everything is left on,
> then the text is just handed back as it was stored. I'm still not
> convinced. :)
> David Trotz wrote:
> > Troy,
> >> Just a note regarding the comment that the SWORD engine take > 6 seconds
> >> to render psalm119...
> >> If this is the case there is a bug somewhere.
> > Perhaps there is a bug, because...
> >> It usually takes < 6 seconds to render an entire Bible to a file on a
> >> low end PC, which I'm guessing is about the same power as todays
> >> My guess is that the extreme amount of tags in the text is taking the
> >> HTML renderer the time.
> > ... it takes my HTML renderer very little time (1s for Psalm 119 w/ full
> > markup in ESV) to render any given text. I have tested this by
> > preloading text from a file then shoving it into the HTML renderer. But
> > as soon as we start to query sword for text from a module we take a
> > significant performance hit. Its only if I turn off all the extra
> > features in the text such as strong's numbers or footnotes in ESV that
> > things are very fast. Perhaps you can look at how we are pulling text
> > from sword and see if there is something wrong with our methodology?
> >> Just trying to pass the buck until someone PROVES to me that we need
> >> optimization in the engine. :)
> > I understand that all too well. ;-)
> > BTW have you given it a run on your new smartphone?
> > In Christ,
> > David Trotz
> > _______________________________________________
> > sword-devel mailing list: sword-devel at crosswire.org
> > http://www.crosswire.org/mailman/listinfo/sword-devel
> > Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel