Contact Us

support@onapp.com

U.S: (+1) 888-876-8666

UK: +44 (0) 203-318-5364

CPU priority is confusing

Completed

Comments

16 comments

  • Avatar
    Stuart Haresnape

    We have some interesting developments coming in this which should resolve the complexities 

    0
    Comment actions Permalink
  • Avatar
    Chris Danks

    HI

     

    Any updates on this? I just updated to 3.1 hoping to see these changes but sadly I can't see anything new on CPU Priority.

    0
    Comment actions Permalink
  • Avatar
    VinaHost

    Hello team,

     

    Any updates on this.

    0
    Comment actions Permalink
  • Avatar
    Stuart Haresnape

    Hi

    We have improved the documentation for CPU priority and you can find this here. 

    https://docs.onapp.com/display/FAQ/Common++Technical+Questions

    I hope this helps - if you have any suggestions on how to improve it further please just send me a message here. 

    Cheers,

    Stuart

    0
    Comment actions Permalink
  • Avatar
    Chris Danks

    VinaHost

    this is simple to fix, make sure your on 3.1+ and in your billing plans, set CPU Prioirty to default to ie 10% & FREE> then set it to hide so it does not show on the slider to customers using that billing plan. this way customers only see Physical CPU cores and not priority.

    0
    Comment actions Permalink
  • Avatar
    VinaHost

    Hello Chris Danks ,

    We  tried this way but it will cause about changing CPU Core for our customer, our can not change CPU core anymore if hide CPU Priority. 

     

    0
    Comment actions Permalink
  • Avatar
    Peter Valadez

    I would suggest that CPU Priority be renamed to "Minimum Guaranteed CPU Cycles" or "Minimum Guaranteed CPU" or just "Guaranteed CPU Cycles". 

    0
    Comment actions Permalink
  • Avatar
    Stuart Haresnape

    Hi - we are still looking at how to simplify this and the language is part of that. I don't have any timescales for any of this but we do have plans to improve. 

    0
    Comment actions Permalink
  • Avatar
    Stuart Haresnape

    We have released a new feature in 3.3.0 called CPU Units. Check it out!

    Stu

    0
    Comment actions Permalink
  • Avatar
    Peter Valadez

    Stuart,

    How can we check this new "CPU Units" feature out?  Looking on https://docs.onapp.com/ it looks like 3.3 is not released yet.  I see the 3.3 documentation listed in the "spaces directory" section of the documentation site, but this site does not allow me to login and it also does not allow me to reset my password, because "no email service has been configured".  I do have a paid license, so I would think I'd be able to do this... 

    0
    Comment actions Permalink
  • Avatar
    Stuart Haresnape

    Hi

    When 3.3.0 is released you will be able to see it. The documentation listing is just a quirk of the software we use. Obviously we have to prepare this in advance but then it has to be hidden until release. You can't get access to hidden documents regardless of what licence you have. 

    Not long now though. 

    Regards

    Stuart

    0
    Comment actions Permalink
  • Avatar
    Peter Valadez

    I don't understand the purpose of adding "CPU Units"; what value does this add?  It is curious to me why Onapp would take something like CPU priority, which people already do not understand, and abstract it even further with CPU Units.  Is this not going in the opposite direction?  With CPU Units, now there are even more calculations needed to understand what it means... and it makes customers' understanding of what resources they are actually getting even less tangible.

    Why not just use MHz, or clock cycles?  And replace priority with "Guaranteed MHz" or "Guaranteed Clock Cycles"... 

    0
    Comment actions Permalink
  • Avatar
    Layla Abdullayeva

    @Peter Valadez the purpose of adding cpu units was to increase flexibility and allow cloud owners set capacity values by themselves by choosing the measurement units they find most suitable- either MHz, bogomips, passmark score, etc.

    0
    Comment actions Permalink
  • Avatar
    Peter Valadez

    @Layla Abdullayeva So can you set the name label that customers will see when they choose how many "cpu units" they want, ex. they will see "MHz" instead of "cpu-units" when they are ordering or logged into the control panel.

    Your explanation makes sense as a way to normalize cpu priority/cores between hosts with different cpu models, which may have different performance benchmarks.  However, a common name for cpu-units on the customer-facing side is definitely needed to avoid the confusion.

    0
    Comment actions Permalink
  • Avatar
    Peter Valadez

    Also, do CPU Units work in a "guaranteed minimum" fashion the same way that CPU Priority does?  With CPU Priority, you are guaranteed a certain amount of cpu processing (as long as the resources aren't over-allocated), and you are able to burst over the amount of processing guaranteed by CPU Priority.  I have not seen this mentioned in the documentation with respect to CPU Units.

    0
    Comment actions Permalink
  • Avatar
    Dominik Nowacki

    Agreed. This would be a really useful feature. I would expand it by a static CPU priority per billing plan.

    0
    Comment actions Permalink

Please sign in to leave a comment.