UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

AR# 51039

2012.2 Vivado - Vivado.exe is using more than 5% of my computer's CPU even though I am not running any processes

Description

I have a design loaded in Vivado Integrated Design Environment 2012.2 and although I do not have any processes like Synthesis or Implementation running, vivado.exe is using a significant percentage of my computer's CPU (>5%).

If I close the Vivado GUI using the stop_gui Tcl command, the CPU usage for Vivado drops to 0%.

What is the GUI checking?

Can this be fixed or changed?

Solution

The Vivado IDE tool has a number of loops that are constantly checking for changes to the project.

The checks primarily check for changes to source files and run results files on disk so that the status of the project can be properly displayed. 

In addition to the checks that are run in Project Navigator, the Vivado IDE also checks the content of sub-project files (EDK projects, IP cores, Sysgen projects, etc.).  

Checking these additional sources in a sub-project can add hundreds of files that are being checked on a constant basis.

Excessive CPU usage has been observed specifically with Vivado projects containing EDK project files. 

To turn off tracking of EDK project source files in the Vivado IDE, do the following:

  1. Close the Vivado project
  2. Open the following file from the project area in a text editor:
    backend_fpga\common\ext_code\K325_backend_EDK.ext\EDK_common_proc_backend.bxml
  3. Search for all occurrences of the first text below and replace them with the second text:

    • search for: IsTrackable="true"
    • replace with: IsTrackable="false"
  4. Save the file
  5. Re-open the project in the Vivado GUI and see if your idle CPU usage now drops to close to 0%.


The checks are only performed when the GUI is up because the purpose is to provide immediate visual feedback to the user when a source file has changed. 

These status checks have been made more efficient in the 2012.3 release.  

 

AR# 51039
Date Created 07/27/2012
Last Updated 05/20/2014
Status Active
Type Known Issues
Tools
  • Vivado Design Suite - 2012.2