henri-c
henri-c3w ago

price below 100

We have introduced a new pricing https://www.windmill.dev/pricing Instead of vCPUs, we are now basing pricing on compute units (a 2GB worker used for a full month). Workers have a size (small, standard, large) based on their memory limit (<=1, (1-2], >2) and each worker size gets a compute unit (0.5, 1, 2) With this new approach, you can now get rid of setting vCPU limits which is an anti-pattern in favor of only setting them as requests not to limit unnecessarily the compute power of your workers Apart from that, seats and discounts for non-profits and SMBs still exist
No description
5 Replies
Alper
Alper3w ago
there seems to be a bug. it says:
Price for workers can't be below $100/mo
but increasing from $25 to $50 lets the message disappear
No description
No description
henri-c
henri-cOP3w ago
Thanks @Alper but how many 'Native workers' have you set? They do count as workers compute units as well, so alert will be displayed if they are set to 0
No description
Alper
Alper3w ago
ah you're right, i didn't see the native workers all good then
Tiago Serafim
Tiago Serafim3w ago
Hey, one clarification. Until very recently, having no native workers was not possible since some features from WM relied on them. Now, in the new price calculator, it does let me set the native workers to 0 and the tooltip says it can be zero. Is that correct?
rubenf
rubenf3w ago
It's the same as currently, you can technically set native workers replicas to 0 but yes we think it's a bad idea however, you can just have no native workers and have the normal workers listen to every jobs so that works