Jump to content

RetroISA constantly eats large amounts of CPU cycles


Recommended Posts

I'm running into the same problem here on an older 8 Core Mac Pro with my process meter showing RetroISA using 199% CPU (almost two whole cores).


Obviously, this is not ideal.


Not sure what the instant scan advanced options change you mentioned is yet. I will see if I can find that and try it.



Retrospect Client 10.0.0 (174)

Link to comment
Share on other sites

I've found the only way to reduce the CPU cycle usage was to exclude all mounted volumes in the config file. My problem now is that the retroISA process continues to consume large amounts of RAM - between 1.18 and 1.25GB. That seems excessive and I have not found a way to reduce it. Killing the process and restarting starts at a few MB but rapidly grows to consume over 1GB in seconds.


Has anyone else observed this?


Today, retroISA process is consuming 1.15GB real memory and 1.22GB virtual memory. On an 8GB system this is a lot of memory to be eating up for one process. This really needs to be corrected along with the excessive CPU usage of the scanning.

Edited by airnorth
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...