The Wolfram Cloud Needs to Be Perfect
The Wolfram Cloud
is coming out of beta soon (yay!), and right now I'm spending much of my time working to make it as good as possible (and, by the way, it's getting to be really great!). Mostly I concentrate on defining high-level function and strategy. But I like to understand things at every level, and as a CEO, one's ultimately responsible for everything. And at the beginning of March I found myself diving deep into something I never expected...
Here's the story. As a serious production system that lots of people will use to do things like run businesses, the Wolfram Cloud should be as fast as possible. Our metrics were saying that typical speeds were good, but subjectively when I used it something felt wrong. Sometimes it was plenty fast, but sometimes it seemed way too slow.
We've got excellent software engineers, but months were going by, and things didn't seem to be changing. Meanwhile, we'd just released the Wolfram Data Drop
. So I thought, why don't I just run some tests myself, maybe collecting data in our nice new Wolfram Data Drop?
A great thing about the Wolfram Language
is how friendly it is for busy people: even if you only have time to dash off a few lines of code
, you can get real things done. And in this case, I only had to run three lines of code to find a problem.
First, I deployed a web API
for a trivial Wolfram Language program to the Wolfram Cloud: