NOTICE: Due to a lapse in annual appropriations, most of this website is not being updated. Learn more.
Form submissions will still be accepted but will not receive responses at this time. Sections of this site for programs using non-appropriated funds (such as NVLAP) or those that are excepted from the shutdown (such as CHIPS and NVD) will continue to be updated.
An official website of the United States government
Here’s how you know
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock (
) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
Characterizing and Back-Porting Performance Improvement
Published
Author(s)
Clif Flynt, Phil Brooks, Donald G. Porter
Abstract
The Tcl interpreter is constantly being modified and improved. Improvements include new features and performance boosts. Everyone wants to use the latest releases with the newest improvements, but corporate users with large code bases may not be able to do this. Reworking an extremely large code base can take longer than the interval between Tcl releases. These users may need a change to be back-ported to the version of Tcl that they are using. A Tcl release includes many changes and identifying the modification that caused a particular performance boost isn't always simple, particularly if the performance boost of interest was a side-effect of other improvements. This paper describes the discovery of a thread-performance issue in Tcl 8.4 which was fixed in 8.5, a semi-automated technique for tracking down the code modification that improved the performance, and a discussion back-porting the improvement.
Flynt, C.
, Brooks, P.
and Porter, D.
(2013),
Characterizing and Back-Porting Performance Improvement, 20'th Annual Tcl/Tk Conference, New Orleans, LA, US, [online], https://tsapps.nist.gov/publication/get_pdf.cfm?pub_id=914992
(Accessed October 2, 2025)