Do you guys have problem with Paseo? Coretime on-demand does not work anymore, please help if you have some leads on how to solve this issue.
3 Likes
You should have posted in “Tech Talk” category i think.
1 Like
I’m looking into this now.
2 Likes
@hgminerva can you be more specific on what is not working anymore? what exactly is happening?
1 Like
I looked into this and replayed your transactions. There are currently no on-demand cores assigned on Paseo. I’ve asked the team to add a core to the pool. There are currently some idle cores so this should be a straightforward fix.
The current error is that the price is too low, but that’s just because the queue has been at 54 every block for quite some time. this is over the ideal demand of 25 and therefore the price has maxed out. It might take some time for the price to come back down to a normal amount.
A bit more details about the symptoms (traffic and therefore spot price are at u128::MAX)
The queue size is small (100), the target usage is low (25%) and the upward correction is super aggressive over that amount. it doesn’t actually take that long for traffic to hit u128::MAX with sustained traffic
but instead of having sustained traffic, we actually just have orders that aren’t draining because paseo has no on demand cores. Once it built up past 25 orders it started to exponentially increase the traffic in each block (we’re now at 54 orders). Since they’re not dropping below 25 it’s at u128 max still.
4 Likes
It appears to be working for me right now, I am able to create blocks for EduChain: https://ondemandui.netlify.app/
You can try it out above with your own chain, but for ours it seems to be working (maybe some cores just got assigned, not sure).
2 Likes
Yes the Paseo team assigned two cores just after 1300UTC on Friday, which drained the queue and the price fell quite quickly.
2 Likes
Thank you so much, the on-demand coretime I think is working now.
2 Likes