Announcement

Collapse
No announcement yet.

Partner 728x90

Collapse

Question on chart update frequency

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Question on chart update frequency

    I notice that on the Chart properties the setting that indicates how often a chart updates doesn't seem to be there any more. In 6.5, we could specify a value of 0 to have it update on every tick, or a value like .2 to have it update every 200 milliseconds. This could be done on a chart-by-chart basis.

    How is this configured now? I know that you have the "Optimized CPU" performance option now in the settings,but I'm not sure if this is related. A little explanation would be good here... in my 6.5 setup I had some short-term charts that were set to update on every tick, and other longer term ones that were updating every half second. Is this type of thing still possible?

    (If it's not it should be... we need to be able to split up processing power to allocate more attention to certain charts, and less attention to others... my 20 second chart should not be held up because a 1440 minute bar is still processing somewhere... )

    #2
    All charts update twice per second now. This is fixed and can't be changed.
    RayNinjaTrader Customer Service

    Comment


      #3
      Originally posted by NinjaTrader_Ray View Post
      All charts update twice per second now. This is fixed and can't be changed.
      Ray, this is a MAJOR, MAJOR, MAJOR problem. You can't have updates twice a second when you are scalping something moving really fast, and I don't want some artificial limitation in your software telling me how often I can see data. Internet lag is bad enough sometimes, but twice a second updates added to that make it even worse.

      I understand that you want to avoid the problems caused by some people setting all the refresh frequencies to zero and then causing you problems by trying to run too much on there, which makes them think that your software is deficient... but you can't solve that problem by just setting everyone to a half-second update. That is not an acceptable solution. This is basically a deal breaker for me if you don't put the ability to update a chart more frequently. If you made it settable to something like 10 times per second, I would probably be happy with that... but twice per second is the type of thing that makes me start to look for another charting package and ask for my money back. Please consider very seriously changing this and allowing at least 100 ms updates. 500 ms is not even close to good enough for some charts.

      I fail to see why you had to remove this when it was already in 6.5, and was used by a lot of people like me... I don't mean to be a jerk about this, but this is an extremely serious problem.
      Last edited by JS999; 10-19-2009, 02:32 PM.

      Comment


        #4
        Originally posted by JS999 View Post
        Ray, this is a MAJOR, MAJOR, MAJOR problem. You can't have updates twice a second when you are scalping something moving really fast, and I don't want some artificial limitation in your software telling me how often I can see data. Internet lag is bad enough sometimes, but twice a second updates added to that make it even worse.

        I understand that you want to avoid the problems caused by some people setting all the refresh frequencies to zero and then causing you problems by trying to run too much on there, which makes them think that your software is deficient... but you can't solve that problem by just setting everyone to a half-second update. That is not an acceptable solution. This is basically a 100% deal breaker if you don't put the ability to update a chart more frequently. If you made it settable to something like 10 times per second, I would probably be happy with that... but twice per second is the type of thing that makes me start to look for another charting package and ask for my money back. Please consider very seriously changing this and allowing at least 100 ms updates. 500 ms is not even close to good enough for some charts.

        I fail to see why you had to remove this when it was already in 6.5, and was used by a lot of people like me... I don't mean to be a jerk about this, but this is an extremely serious problem.
        I appreciate your candid feedback on this and will add your suggestion to my beta feedback list.
        RayNinjaTrader Customer Service

        Comment


          #5
          Originally posted by NinjaTrader_Ray View Post
          I appreciate your candid feedback on this and will add your suggestion to my beta feedback list.
          Well, what exactly are the chances of this getting added? Is this a feature that requires serious architectural changes now with the way you guys have written version 7, or is it something that could be changed without too much trouble?

          Comment


            #6
            Originally posted by JS999 View Post
            Well, what exactly are the chances of this getting added? Is this a feature that requires serious architectural changes now with the way you guys have written version 7, or is it something that could be changed without too much trouble?
            All of the feedback that I receive will be seriously considered but only after the beta has been out for sometime to properly guage demand and prioritize any changes. Its just too soon to tell if this would be changed or not.
            RayNinjaTrader Customer Service

            Comment


              #7
              Originally posted by NinjaTrader_Ray View Post
              All of the feedback that I receive will be seriously considered but only after the beta has been out for sometime to properly guage demand and prioritize any changes. Its just too soon to tell if this would be changed or not.
              OK... I guess what I was really getting at though, is how hard it's going to be to change it. I would like to have an assessment of this, since I don't know how much time/effort it would take you guys to make it work on a per-chart basis like 6.5. That will factor into my decisions of what to do.

              Also, I know for a fact that it would take you literally about 15 minutes of programmer time (I bet I could do it 5 minutes myself) to set up a simple textbox with an input that asked the user how many times per second they wanted to refresh, and set your timer interval to that. You don't have to go and change the architecture to make it work on a per-chart basis, but at least give us the ability to modify it globally. That is absolutely no work at all on your part, and could be out in the next release. There is absolutely no reason to not allow us to do this, since it was a feature in 6.5 and many people will be expecting it in 7.

              I understand that you don't want some people complaining about performance as I said, but you can't just cripple the software for the rest of us for that reason... we should still be able to run it the same as we did in 6.5, or at least close to it. I am going to start a poll on this in another forum so you can get a gauge of how many people are interested in this.

              Comment

              Latest Posts

              Collapse

              Topics Statistics Last Post
              Started by Geovanny Suaza, 02-11-2026, 06:32 PM
              0 responses
              599 views
              0 likes
              Last Post Geovanny Suaza  
              Started by Geovanny Suaza, 02-11-2026, 05:51 PM
              0 responses
              345 views
              1 like
              Last Post Geovanny Suaza  
              Started by Mindset, 02-09-2026, 11:44 AM
              0 responses
              103 views
              0 likes
              Last Post Mindset
              by Mindset
               
              Started by Geovanny Suaza, 02-02-2026, 12:30 PM
              0 responses
              558 views
              1 like
              Last Post Geovanny Suaza  
              Started by RFrosty, 01-28-2026, 06:49 PM
              0 responses
              558 views
              1 like
              Last Post RFrosty
              by RFrosty
               
              Working...
              X