Thread

Actually, I believe we can stop here.  http://textile.thresholdstate.com/.  The speed problem is with Textile, parsing large HTML tables it would appear.  So I guess my question is: why are you using Textile when your tables are all written in HTML in the articles?

Yikes - Script Executed in 443.0274 seconds - after putting in the 3/16/2007 dated textile.

The wiki article with page_content that’s ~43rows X 8col HTML table (with no links) shows the following:

(164.119278) Line 1544 done with array and setting up article
(279.996296) Was Line 1544 split out code for article after part 1
(404.353051) Was Line 1544 split out code for article after part 2

-C

re: “why are you using Textile”
Lotsa users - techie folks tend to like posting articles as HTML (some from Dreamweaver, Frontpage, etc) and non techie folks like the Textile way as they aren’t comfortable with the HTML tables. (I even wrote up an Excel VBA macro to take a range from a spreadsheet and convert it to text html table.)

Is there an alternative method of formatting that you would recommend for non technical folks to get tabular format in the wiki entry? I’m totally up for alternatives.

You might try Markdown and see if it’s more performance friendly.  Not sure if you tried one of your test tables on textile.thresholdstate.com that I linked to above, but if you do, you’ll see that it’s just not efficient at working with that text.  If I had to guess, it would be at least partly due to the full content of the article being on a single line.  Markdown may have the same issue, but it’s worth a try.  In the end, the solution could possibly be that simple: not putting the entire table on a single line.

Thanks, Derek, for all the deep digging and advice. I’ll play around with other text formatting options and also with the HTML table entries and see if there is a way to speed things up. I’ll post back for any others who may encounter the same.
Your help tracking this down is very much appreciated!

Carolyn, there are times when I just put up an html table and then make a screen shot of that and use the image instead. Unless you need to update the items in that table, it’s a quick and dirty workaround.

Thanks, Sue, but my folks need to update the data in the wiki tables regularly as they are being used as a type of dashboard.

I think I found just the trick I need for these HTML tables in the short term (until I can explore alternatives for formatting)...
On the textile site linked in Derek’s post above, once can “bypass” textile on raw HTML by surrounding the HTML with two equals signs (==).
Doing this on the two notable tables brought response to 50.4495 seconds for Recent Changes instead of 400+.

Thanks to all who contributed. Now onto that new build update…

Great! Glad you were able to redo things with Derek’s help.