Mike Gerwitz
b7372fe7cd
This takes a bunch of individual templates and combines them into one, while also utilizing the already-available symbol table map in place of using an XPath on `preproc:symtable`. The results are much more drastic than I was expecting. I was exploring this because one of our largest packages was spending most of its time (~5m) in fragment compilation, which was a surprise to me. Prior work I did for runtime optimizations led to optimizations in its parent `js.xsl`, but not in `js-calc.xsl`, which has largely been untouched since it was originally written for XSLT 1 over 10 years ago. Because it was originally written for XLST 1, it does not take advantage of maps, tunneling variables, or various other options. Further, it was written in a naive way that was convenient (and clear) at the time, and wholly acceptable for smaller inputs. But, as is the case with quadratic-time systems, there are severe growing pains. This change reduced the package compilation time from 5-6m down to 1m15s, and this was just the first attempt at optimizing it. I should have taken a look at this long ago, but my efforts were focused on TAMER, and I didn't want to divert that focus. That was a mistake. Symptoms of this problem were already prevalent ~10 months ago, when the package was taking 3 minutes to compile (so the time has since doubled). This also eliminates `@magic`, which has not been used for a long time (it used to be used for a "constant" that held the current date/time; such a value is now passed into the system like any other input). After making this change, the resulting packages are byte-for-byte identical. I also noticed, though I haven't tried to measure it, that there seem to be fewer multi-core spikes; this is possibly related to Saxon not trying to evaluate expensive `template/match` expressions concurrently anymore. If true, this will also help with resource contention for parallel builds. DEV-15095 |
||
|---|---|---|
| bin | ||
| build-aux | ||
| core | ||
| design/tpl | ||
| doc | ||
| progtest | ||
| rater | ||
| src | ||
| tamer | ||
| test | ||
| tools | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .gitmodules | ||
| .rev-xmle | ||
| .rev-xmlo | ||
| COPYING | ||
| COPYING.FDL | ||
| HACKING | ||
| Makefile.am | ||
| README.md | ||
| RELEASES.md | ||
| VERSION.in | ||
| bootstrap | ||
| c1map.xsd | ||
| configure.ac | ||
| package-lock.json | ||
README.md
TAME
TAME is The Algebraic Metalanguage, a programming language and system of tools designed to aid in the development, understanding, and maintenance of systems performing numerous calculations on a complex graph of dependencies, conditions, and a large number of inputs.
This system was developed at Ryan Specialty Group (formerly LoVullo Associates) to handle the complexity of comparative insurance rating systems. It is a domain-specific language (DSL) that itself encourages, through the use of templates, the creation of sub-DSLs. TAME itself is at heart a calculator—processing only numerical input and output—driven by quantifiers as predicates. Calculations and quantifiers are written declaratively without concern for order of execution.
The system has powerful dependency resolution and data flow capabilities.
TAME consists of a macro processor (implementing a metalanguage), numerous compilers for various targets (JavaScript, HTML documentation and debugging environment, LaTeX, and others), linkers, and supporting tools. The input grammar is XML, and the majority of the project (including the macro processor, compilers, and linkers) is written in a combination of XSLT and Rust.
TAMER
Due to performance requirements, this project is currently being reimplemented in Rust. That project can be found in the tamer/ directory.
Documentation
Compiled documentation for the latest release is available via our GitLab mirror, which uses the same build pipeline as we do on our internal GitLab instance. Available formats are:
Getting Started
To get started, make sure Saxon version 9 or later is available and its path
set as SAXON_CP; that the path to hoxsl is set via HOXSL; and then run
the bootstrap script:
$ export SAXON_CP=/path/to/saxon9he.jar
$ export HOXSL=/path/to/hoxsl/root
$ ./boostrap
Running Test Cases
To run the test cases, invoke make check (or its alias, make test).
Testing Core Features
In order to run tests located at core/test/core/**, a supporting environment
is required. (e.g. mega rater). Inside a supporting rater, either check out a
submodule containing the core tests, or temporarily add them into the
submodule.
Build the core test suite summary page using:
$ make rater/core/test/core/suite.html
Visit the summary page in a web browser and click the Calculate Premium button. If all test cases pass, it will yield a value of $1.
Hacking
Information for TAME developers can be found in the file HACKING.
License
This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.