CA offers minimal public information pertaining to the performance drain the usage of some objects and operators introduce to processing. As an example, swim lanes within a process provide an excellent means of organizing operators within a process, but they can introduce substantial performance issues. As another example, it’s better to perform verbose JavaScript execution within a Run JavaScript operator instead of within another operator’s pre- or post-execution script. As yet another example, it’s better to hard-code variables within the process dataset as opposed to creating the variables at run-time. The biggest issue for me is its lack of support for current JavaScript methods and functions, which makes scripts unnecessarily longer than they need to be. It seemed I could only rely on the methods and functions available in ECMA 1 (which was released in 1997), but that wasn’t a deal-breaker and the product is capable of extending its capabilities through the inclusion of other code libraries.
