You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Counting power cycles might not be ideal for some environments with frequent power outages as the licence would expire too often and that would probably result in angry refund requests. Also, in enviromnents where a CPU runs almost forever without a power cycle, for example, in data centers, the licence would effectively turn into a one-time purchase. I think a higher customer lifetime value could be achieved with a monthly payment system. "Pay as you game!", "Rent your own CPU for as low as $5/mo" - there are lots of marketing opportunities here to unlock.
Another idea: consider achieving even more granularity of payments by applying the same technique in a per-core model.
The text was updated successfully, but these errors were encountered:
I think we should move it to a CaaS system (CPU as-a-service) where your CPU would be somewhere else in the world and use internet to communicate to the socket using a separate Intel Box:tm: directly from Intel's CPUServer
Counting power cycles might not be ideal for some environments with frequent power outages as the licence would expire too often and that would probably result in angry refund requests. Also, in enviromnents where a CPU runs almost forever without a power cycle, for example, in data centers, the licence would effectively turn into a one-time purchase. I think a higher customer lifetime value could be achieved with a monthly payment system. "Pay as you game!", "Rent your own CPU for as low as $5/mo" - there are lots of marketing opportunities here to unlock.
Another idea: consider achieving even more granularity of payments by applying the same technique in a per-core model.
The text was updated successfully, but these errors were encountered: