Home > Community > Blogs > Functional Verification > specman 9 2 preview a fresh profile on the profiler
Login with a Cadence account.
Not a member yet?
Create a permanent login account to make interactions with Cadence more convenient.

Register | Membership benefits
Get email delivery of the Functional Verification blog (individual posts).


* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

Specman 9.2 Preview: A Fresh Profile on the Profiler

Comments(0)Filed under: Functional Verification, e, Specman, IES-XL, performance, team specman

[Preface: all features in the 9.2 preview series are in Beta now.  We invite you to sign-up for the beta program and give this feature a test drive!]
[Team Specman welcomes Avi Bloch from Specman R&D to introduce one of “his” new features.]

Starting in Specman/IES-XL 9.2, users will be able to split the profiling process into separate run and analysis phases. This allows users to generate a profiler report regardless of how the test ended, and enables the creation multiple reports from the same profiler data.

Problem Statement
In the current profiler use model (versions 8.2 and earlier), the user can run the profiler either by running the “sn_profile.sh” utility, or by using the “set profile” command.  In both cases, Specman executes a run and generates a profiler report.  However, it’s advantageous to enable users to split this process into two parts: the first part consists of running the test while gathering profile information; and the second part will generate the report.  This will allow generating a profiler report regardless of how the test completes (even if the run crashes).  Additionally, with new filtering mechanisms added to the report generation command set, you will be able to generate multiple reports from the same profiler data, saving you valuable compute time.

Solution Overview
The following options have been added to the “set prof” command to support the capabilities described above:

By default, if a previous “set profile” command was executed during the current run in which the report_dir was specified, this specified report directory will be used.  Otherwise Specman will look for the profiler information in the directory of the form ./sn_prof.<process_id> directory with the latest modified date. This option lets you specify the output directory that was used during the desired profiler run.

Tells Specman not to generate a report at the end of the run. In addition, it tells Specman not to remove the temporary data used for generating the profiler report (so you can reference the profile data a later time)

Specifies the name of the report. Default is report_cpu.html or report_mem.html depending on the mode of the profiler.


set profile -generate

will generate a profile report based on a previous run of the profiler.  Note that -generate can be executed in stand-alone Specman even if the actual run was done with a simulator and/or compiled/loaded code.

I hope you find these new options useful, and I invite you to send me any questions or feedback by posting a comment below, or forward them via Team Specman.

Happy Profiling!

Avi Bloch
Specman R&D


Leave a Comment

E-mail (will not be published)
 I have read and agree to the Terms of use and Community Guidelines.
Community Guidelines
The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.