spk-logo-tm-2023
0%
1-888-310-4540 (main) / 1-888-707-6150 (support) info@spkaa.com
Select Page

Electric Commander: Performance Comparison Between ectool and ec-perl

windchill features best plm software
Written by SPK Blog Post
Published on April 29, 2015

Prior to version 5.2, Electric Commander has offered two primary ways to access the API for scripting purposes: ectool and ec-perl. Both allow users to accomplish virtually any task within Commander, but it’s important to note there is a significant performance difference between the two.

Ectool remains an excellent choice for quick operations on the command line or embedded in a script, however any significant interface with the Commander server that requires multiple API calls is best accomplished using ec-perl. Ectool gets beats because for each command, ectool opens a connection to the commander server, issues the command, and closes the connection. When done repeatedly, this adds a significant amount of overhead to a given sequence of operations.

Ec-perl, on the other hand, opens a single, persistent connection with the Commander server, allowing for multiple operations to be executed quickly. Additional speed can be gained by submitting batch requests through ec-perl. A batch request bundles multiple server requests together (such as get or setProperty requests) and transmits them to the server together as a single request, further reducing network burden.

For demonstrations purposes, I created a Commander procedure that performs 500 getProperty requests and 500 steProperty requests using ectool, ec-perl, and ec-perl with batch requests.

Electric Commander 1 Electric Commander 2 Electric Commander 3

As the graphs indicate, ec-perl performs getProperty operations 28 to 113 times faster than ectool and can perform setProperty operations 4 to 15 times faster than ectool. This should clearly demonstrate that ec-perl is the superior method for scripting Commander operations that require multiple API calls. For some, Perl may not be a preferred language, but if speed is really a concern, it’s worth the effort to code your scripts that do the heavy lifting using ec-perl.

Next Steps:

David Hubbell
Software Engineer
SPK and Associates

Latest White Papers

Rovo Product Guide: Key use cases across your organization

Rovo Product Guide: Key use cases across your organization

Gen-AI is making its way into nearly all of our tools, and the Atlassian toolkit is no exception. This eBook explores use cases for Atlassian’s AI agent, Rovo. What You Will Learn In this eBook, you will discover how Rovo can help: Engineers ITSM Teams Business...

Related Resources

GitHub Actions to GitLab CI Migration Checklist

GitHub Actions to GitLab CI Migration Checklist

As organizations look to simplify their DevOps toolchain, improve cost predictability, and strengthen security, many are making the shift from GitHub Actions to GitLab CI.  This eBook provides a step-by-step migration checklist to help engineering teams transition...

Rovo Product Guide: Key use cases across your organization

Rovo Product Guide: Key use cases across your organization

Gen-AI is making its way into nearly all of our tools, and the Atlassian toolkit is no exception. This eBook explores use cases for Atlassian’s AI agent, Rovo. What You Will Learn In this eBook, you will discover how Rovo can help: Engineers ITSM Teams Business...

How and Why to Standardize Onto One CAD Platform

How and Why to Standardize Onto One CAD Platform

Many engineering teams rely on multiple CAD systems across teams. The issue withusing multiple CAD tools is that it can lead to delays and innefficiencies. This white paper explores the benefits of consolidating onto one CAD platform.What You Will Learn In this white...