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

Introducing Atlassian’s Service Collection

Introducing Atlassian’s Service Collection

Are you looking for new tools that empower your teams to deliver exceptional service experiences? Atlassian’s Service Collection ensures great service for both employees and customers. What You Will Learn In the following eBook, you will discover: The tools and...

Related Resources

GitLab and Gemini: Agentic Software Development on Google Cloud

GitLab and Gemini: Agentic Software Development on Google Cloud

Key takeaways Agentic software development goes beyond AI coding assistants: GitLab Duo Agent Platform gives AI agents context across issues, source code, merge requests, CI/CD pipelines, security findings, and development history. GitLab and Gemini combine lifecycle...

5 Ways to Reduce Engineering Cycle Time Without Adding Headcount

5 Ways to Reduce Engineering Cycle Time Without Adding Headcount

Key takeaways Faster engineering does not always require more headcount: Disconnected systems, manual handoffs, rework, and poor visibility often create more delays than a lack of engineering capacity. A digital thread can eliminate major sources of wasted time:...