Changed Database Service Tier resulted in lots of "Timeout-expired-errors"

Question

Last night I changed database service tier from Web Edition to Standard S0. Since then we are getting a lot of errors like this:
"Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding."
Before the change we had no such errors. I have tried to make a new deployment of our cloud services but it doesn't change anything. It still fill the error logs with timeout-expired-errors and the site itself seems to be significantly slower than before.
What's the problem? I assume the Standard S0 service tier should be sufficient in performance. We don't have much traffic on the site. 
Hope someone can shed a light...

Answer 1

Folks we know that changing business models is a hard thing to do.  In the Web/Business case, you pay on size of the DB and you get whatever performance we have at the time.  Sometimes this is great, other times this is ok and sometimes performance
is very poor.  Customers have given us feedback that this unpredictable performance is very difficult to deal with.
Using this feedback as a key input, the business model for Basic/Standard/Premium is $/perf.  As Jan points out below, understanding what resources your consuming is a great first step before moving to B/S/P.
Your mileage may vary here.  Many customers see a decrease because of this business model change.  Others see no impact, and some will see an increase if their DBs are very small and consume a lot of resources.
Jan, I and the team would be happy to help customers move into the new business model.  To have great conversations will need some customer specifics that aren't best shared in a public forum.  guyhay@microsoft is my email if you'd like to have
that conversation.