Changes between Version 20 and Version 21 of GenshiPerformance
- Timestamp:
- Sep 12, 2006, 12:15:11 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GenshiPerformance
v20 v21 1 = Performance of the MarkupTemplate Engine =1 = Performance of the Genshi Template Engine = 2 2 3 The directory [source:/trunk/examples/bench/ examples/bench] has some very simple benchmarks to compare the performance of Markupto other template engines.3 The directory [source:/trunk/examples/bench/ examples/bench] has some very simple benchmarks to compare the performance of Genshi to other template engines. 4 4 5 5 ''It should be noted that text-based template engines generally have a '''lot''' less work to do than XML-based ones, simply because their functionality is limited to processing text as opposed to processing markup.'' … … 12 12 13 13 || '''Template Engine''' || '''Rendering time (less is better)''' || '''Notes''' || 14 || Markup|| 4.05 ms || ||14 || Genshi || 4.05 ms || || 15 15 || [http://www.clearsilver.net/ Clearsilver] || 0.33 ms || !ClearSilver is a text-based template engine written in C. || 16 16 || [http://www.djangoproject.com/documentation/templates/ Django] || 1.84 ms || Text-based template engine that comes with the [http://www.djangoproject.com/ Django] framework. || … … 18 18 || [http://www.owlfish.com/software/simpleTAL/ SimpleTAL] || 3.13 ms || Another XML-based template engine written in Python, based on the [http://www.zope.org/ Zope] template engine (TAL). || 19 19 20 The test template is rather simple right now and doesn't make much use of the advanced features provided by either Markupor Kid, because then it would be impossible to implement an equivalent template using other template languages.20 The test template is rather simple right now and doesn't make much use of the advanced features provided by either Genshi or Kid, because then it would be impossible to implement an equivalent template using other template languages. 21 21 22 22 == `bigtable` benchmark == … … 25 25 26 26 || '''Template Engine''' || '''Rendering time (less is better)''' || '''Notes''' || 27 || Markup|| 661 ms || ||27 || Genshi || 661 ms || || 28 28 || [http://kid-templating.org/ Kid] || 720 ms || || 29 29 || [http://www.djangoproject.com/documentation/templates/ Django] || 357 ms || || … … 34 34 == Another benchmark == 35 35 36 There's another simple benchmark in the Markup repository: [source:/trunk/examples/basic/ examples/basic]. That example is however only implemented for Markupand Kid. Here are the numbers:36 There's another simple benchmark in the Genshi repository: [source:/trunk/examples/basic/ examples/basic]. That example is however only implemented for Genshi and Kid. Here are the numbers: 37 37 38 38 || '''Template Engine''' || '''Rendering time (less is better)''' || '''Notes''' || 39 || Markup|| 4.00 ms || ||39 || Genshi || 4.00 ms || || 40 40 || [http://kid-templating.org/ Kid] || 8.93 ms || || 41 41 42 I'm not quite sure why the difference between Markupand Kid is so much more drastic in this example compared to the above. It does define more (and slightly more sophisticated) match templates, which would suggest that Markup implements those more efficiently. However, that's just a theory.42 I'm not quite sure why the difference between Genshi and Kid is so much more drastic in this example compared to the above. It does define more (and slightly more sophisticated) match templates, which would suggest that Markup implements those more efficiently. However, that's just a theory.