CCS: Code Composer Studio V8.2 High CPU usage in windows 7

Hello Khairil,

try to disable Remote System Explorer (RSE UI) an let me know.

still high cpu usage at randomly period of time.

surprisingly i don't get this problem when I move to desktop computer with windows 10.

What CPUs, how much RAM, SSD/HDD on both machines?

Right now it is my guessing, but looks to me that your CCS memory allocation is too small.
Close all firefox tabs and instances on your laptop and observe CPU usage after disk I/O drops dowm.

Could you post your JVM settings on a laptop?
File name: eclipse.ini
and in my case the path is: C:\ti\ccs820\ccsv8\eclipse\

Khairil - A common culprit for this is the indexer. As a test, can you try temporarily disabling it to see if it helps?
software-dl.ti.com/.../ccs_project-management.html

Thanks
ki

Thanks ki

but the problem persist.
well eclipse has a lot problem anyway, is there any chance that this is due to corrupt installation?
before this I uninstall previous version because the TIrex is failed to open. even now there is I can not open pinmux config inside CCS

I don't think so. I have 8GB mem on my laptop
here is eclipse.ini

-startup
plugins/org.eclipse.equinox.launcher_1.4.0.v20161219-1356.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.551.v20171108-1834
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-Dosgi.requiredJavaVersion=1.8
-Xms40m
-Xmx512m
--add-modules=ALL-SYSTEM

Your picture shows that firefox is major memory consumer on your lap.
Your CCS declares (-Xmx512m) 512 MB for Java heap. If parts of Java heap are page outed you could be hit by a dramatic performance drop.

Tirex does a lot of I/O operations when starting and in case of a weak filesystem caching it just timeouts.
On old laptop with 8 GB, a few firefox sessions I need to try 3-4 times to start Resource Explorer and it takes even more than 15 minutes.
All this because of too small RAM memory.

You can try bumping up the max heap size to 768m:
processors.wiki.ti.com/.../FAQ_-_CCSv7

Can you also try using a clean new workspace and see if the CPU load is low (initially)