Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
To Lars
Hi Lars,

Nice work there!
But I would suggest, to improve performance, you could do serverside URL caching?
I'm a developer and know about this challenge.

Since the NT does not change so quickly, headers could be set to public caching (instead of private) and if I click 'back', a expiration header, could cause the page to be cached in the browsers cache, currently, it seems that all PHP scripts do a round-trip to the DBMS.

Hi Distazo,

Thank you for your suggestions. I totally agree with you that some parts of dukhrana could use a performance boost. Each new feature that I have recently added has unfortunately brought with it, more or less, a performance hit to the site. As a remedy for this I have been contemplating on pre-rendering some parts and instead serve them as static pages (the verse analysis pages for example). This approach would make a great speed improvement, especially since the content doesn't change very often. On top of this I have a few algorithms used by the Peshitta Tool that I have been wanting to optimize for some time.

I will also have to look into the possibilities of caching, but since I don't run dukhrana on my own server I'm pretty limited when it comes to tweaking Apache itself. Any tips you have please feel free to share with me. You can always reach me at ljl at dukhrana dot com :-)

Hi akhi Lars,

I'd look at the W3C http logs, and see what's causing the most CPU and taking the most resources.

In my case, (I also host a bible translation), 25% would be caused by web robots, looking for new / updated content, which is a waste of performance.

(I do not program perl, but could do this <!-- sSmile --><img src="{SMILIES_PATH}/smile.gif" alt="Smile" title="Smile" /><!-- sSmile --> the code is C#

<!-- m --><a class="postlink" href=""></a><!-- m -->

In my solution, each page, and chapter, the 'bible engine' calculates a ETAG using each primary key + timestamp per verse (because verses can be updated). So, a whole chapter or verse selection, can be precalculated an ETAG, and you will see performance improvements.
Shlama akhi Distazo,

I spent this weekend optimizing and redesigning some parts of the dukhrana code. My efforts turned out to be successful as both the load times and overall performance of the site have significantly improved! And to top it off, I have, as an experimentation, added support for conditional GET caching for the analyze_verse.php, concordance.php, lexeme.php and word.php pages! I really must say... dukhrana has never been this fast and snappy before! So you better hold on to your hat next time you pay a visit =)

Thanks for inspiring me to do these improvements! :-D

Push b'shayna,

I'm happy i've inspired you <!-- sSmile --><img src="{SMILIES_PATH}/smile.gif" alt="Smile" title="Smile" /><!-- sSmile -->

ps: Soon, I will publish the Dutch translation of the Peshitta at <!-- w --><a class="postlink" href=""></a><!-- w -->

Maybe, we could make a SOAP contract so that dukhrana also can publish the Dutch translation and vice versa about the Aramaic text? (which I would like to have at my site as well)
Sure! I'm sure we can work something out :-)

Forum Jump:

Users browsing this thread: 1 Guest(s)