Changes between Version 16 and Version 17 of GenshiPerformance
- Timestamp:
- Aug 3, 2006, 6:02:11 PM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
GenshiPerformance
v16 v17 16 16 || [http://www.clearsilver.net/ Clearsilver] || 0.33 ms || !ClearSilver is a text-based template engine written in C. || 17 17 || [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 || [http://kid-templating.org/ Kid] || 5. 66ms || Kid templates are compiled to Python byte-code. The cElementTree implementation was used for this test, although using the Python implementation doesn't appear to make a significant difference. ||18 || [http://kid-templating.org/ Kid] || 5.12 ms || Kid templates are compiled to Python byte-code. The cElementTree implementation was used for this test, although using the Python implementation doesn't appear to make a significant difference. || 19 19 || [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). || 20 20 … … 28 28 || Markup || 878 ms || || 29 29 || Markup + Speedups || 644 ms || [source:/branches/experimental/speedups Experimental Markup branch] that implements some core portions in C. || 30 || [http://kid-templating.org/ Kid] || 879ms || ||30 || [http://kid-templating.org/ Kid] || 720 ms || || 31 31 || [http://effbot.org/zone/element-index.htm ElementTree] || 329 ms || ''Not a template engine'': the benchmark simply constructs the XML tree in memory and serializes it. || 32 32 || [http://effbot.org/zone/celementtree.htm cElementTree] || 202 ms || ''Not a template engine'': the benchmark simply constructs the XML tree in memory and serializes it. || … … 40 40 || Markup || 3.67 ms || 41 41 || Markup + Speedups || 3.61 ms || 42 || [http://kid-templating.org/ Kid] || 9.45ms ||42 || [http://kid-templating.org/ Kid] || 8.93 ms || 43 43 44 44 I'm not quite sure why the difference between Markup 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.