That's one thing, atleast on my board. Rendering posts takes time, and especially, running them through the post filter.


Some possible optimizations, mostly discussing them:


Storing posts preparsed to a point

* can't fully preparse them as some markup will be dynamic (/me, user tag, etc)
* very little work when rendering posts
* any change to markup requires reparsing all the posts (can be done by just marking them dirty and reparsing them when needed, but eh, complication)
* takes twice as much DB space (need to keep the original post)


Detecting which tags are present before running the postfilter
... and only running the needed filters

* would probably only benefit big posts if done on individual tags
* could benefit a lot of posts if done on a global level though (ie. if post contains no BBCode at all, skip a big chunk of the postfilter)



Oh and PHP also has an extension for parsing BBCode. It won't be available everywhere, but it's still worth looking into. They say it's faster than using regexes, and it looks flexible too.

____________________
Kuribo64 - melonDS

want some revolution in your coffee?

Well I applied the big optimization to my board (do not run BBCode filters if no BBCode is present)...


According to what I got, only 25% of the posts contain BBCode. Yet, the optimization gives little to no change.

____________________
Kuribo64 - melonDS

want some revolution in your coffee?