+1 888 340 6572 GET STARTED
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-1773 » Open Feature request MC-2320

CPU / RAM / Memory usage monitor

Go to the next issue (open or closed)
Go to the next open issue

This is a request for a resource monitor to find which charts/processes/studies are using the most computer resources.

Maybe you forgot to turn off "update on every tick" and it's slowing down the whole platform?
Or you have too many charts open in one workspace, or forgot about that 1 tick chart?
Tradestation has something similar and it was helpful.
In my case all of my charts are freezing in the most active periods of the market and I am trying to track down the culprit.

Comments (3)
user-offline.png  RockyLee (rockylee)
Sep 12, 2017 - 16:06

Yes it would be usefull, since I often get low memory popup

user-offline.png  FidelisCapital (Fidelis)
Oct 03, 2017 - 14:00

A change like this makes sense. But, I think the platform could do with some major changes that would make this idea a very small thing. I would like MC Development to look at a platform that I recently demoed called Algoterminal. It has all of these things and more. I think MC should take idea from it and improve MC in the next upgrade. Please look at my recommendations



user-offline.png  charlesscitco (charlesscitco)
Nov 30, 2017 - 23:15

That memory pop up is annoying. I have other platforms that dont ever do that. It is only MC and I dont know why if the others dont have any problem.

Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates