TP3 Optimizations

Hello Everyone,

How’s the experience with TP3 thus far?

How’s the processing speed coming along?

Have you tested it on large websites?

I’ve being looking into some ways to optimize the code. From my little tests I’ve found that Etomite 0.6 runs faster than TP3 due to the fact that the parser is embedded insde the index.php file. When I embedd the document parser inside TP3’s index.php file I got similar performance of Eto 0.6. I think the "include" statement tends to slow things down a bit (in milliseconds). Another thing is the DISTINCT keyword but I’ll soon find a way around that.

From of my basic test I was able to render pages on .02ms on a 800mhz duron pc.

Do you guys have any suggesstions on how to speed up TP3?

Quote from: xwisdom at Jul 11, 2005, 12:16 PM

Hello Everyone,

How’s the experience with TP3 thus far?

How’s the processing speed coming along?

Have you tested it on large websites?

I’ve being looking into some ways to optimize the code. From my little tests I’ve found that Etomite 0.6 runs faster than TP3 due to the fact that the parser is embedded insde the index.php file. When I embedd the document parser inside TP3’s index.php file I got similar performance of Eto 0.6. I think the "include" statement tends to slow things down a bit (in milliseconds). Another thing is the DISTINCT keyword but I’ll soon find a way around that.

From of my basic test I was able to render pages on .02ms on a 800mhz duron pc.

Do you guys have any suggesstions on how to speed up TP3?

Is it possible to only put the parsing related code inside of our index.php and leave the API’s isolated in an include? And would this bring us similar performance to moving all of it into index.php, or would the API’s being in an included file prevent the higher-performance parsing behavior?

Quote from: OpenGeek at Jul 11, 2005, 12:46 PM

Is it possible to only put the parsing related code inside of our index.php and leave the API’s isolated in an include?? And would this bring us similar performance to moving all of it into index.php, or would the API’s being in an included file prevent the higher-performance parsing behavior?

Well from what’s available of the web it would seem to me that it’s better to include the document.parser inside the index.php file:

http://www.sitepoint.com/forums/showthread.php?t=162343&page=1&pp=25

What we could do is make this an optional feature. we can add an option inside the manager to compile/optimize the site (any one have a good name for this?). This feature would autmatically merge the documentparser and siteCache.idx files into the index.php file. This would offer some milliseconds speed improvement which would eventually add up for large website traffic.