Question

I want to have one free dyno working for my JAVA test application.

I suspect that I already have this and that there is a bug in heroku info.
However the app is really slow. The strange thing is that only I use the app so very little load is applied. The app should be fast and optimized as it’s a small sample app done with spring roo as per the heroku tutorial. If run locally on my laptop the performance is magnitudes better than heroku.

What do you say is it simply a bug in the heroku info command or do I have 0 dynos?

$ heroku info //Shows 0 dynos

....
Dynos:          0
Workers:        0
Repo size:      75M
Slug size:      61M
Stack:          cedar
Data size:      32k
Addons:         Basic Logging, Basic Release Management, Shared Database 5MB

$ heroku ps //I interpret this as 1 dyno; correct?

Process       State               Command
------------  ------------------  ------------------------------
web.1         up for 30m          java $JAVA_OPTS -jar target/depend..

$ heroku scale web=1 //Try to force 1 dyno

Scaling web processes... done, now running 1

$ heroku info //Stills shows 0 dynos

....
Dynos:          0
Workers:        0
Repo size:      75M
Slug size:      61M
Stack:          cedar
Data size:      32k
Addons:         Basic Logging, Basic Release Management, Shared Database 5MB

Answer 1

I’m not sure why heroku info doesn’t show the dyno but if heroku ps shows one then you are using one. It shouldn’t be slow, except that the first request to each page will cause the JSP to be compiled. But after it is compiled things should be fast. For comparison, here is the Spring Roo Pet Clinic app running on Heroku:
http://blazing-window-406.herokuapp.com/