Here is a simpler set of symptoms that (at least for now) vindicates
bootstrap datepicker.
Heroku:
2013-12-05T18:50:02.485929+00:00 app[web.1]: Started GET "/admin/agents"
for 71.43.119.234 at 2013-12-05 18:50:02 +0000
2013-12-05T18:50:02.519716+00:00 app[web.1]: Processing by
Admin::AgentsController#index as H
TML
2013-12-05T18:50:02.973171+00:00 app[web.1]: DRYML: Compiled
app/views/taglibs/auto/admin/rapid/cards.dryml in 0.25s
2013-12-05T18:50:05.715316+00:00 app[web.1]: DRYML: Compiled
app/views/taglibs/auto/admin/rapid/pages.dryml in 2.74s
2013-12-05T18:50:05.858354+00:00 app[web.1]: DRYML: Compiled
app/views/taglibs/auto/admin/rapid/forms.dryml in 0.14s
2013-12-05T18:50:33.507291+00:00 app[web.1]: E,
[2013-12-05T18:50:33.507038 #2] ERROR -- : worker=0 PID:19 timeout (31s
> 30s), killing
2013-12-05T18:50:33.576755+00:00 app[web.1]: E,
[2013-12-05T18:50:33.576590 #2] ERROR -- : reaped #<Process::Status: pid
19 SIGKILL (signal 9)> worker=0
Local:
Started GET "/admin/agents" for 127.0.0.1 at 2013-12-05 13:49:17 -0500
Processing by Admin::AgentsController#index as HTML
DRYML: Compiled
/home/donz/.rvm/gems/ruby-2.0.0-p247/gems/dryml-2.0.1/taglibs/core.dryml
in 0.03s <<< This one is missing above.
DRYML: Compiled app/views/taglibs/auto/admin/rapid/cards.dryml in 0.20s
DRYML: Compiled app/views/taglibs/auto/admin/rapid/pages.dryml in 1.34s
DRYML: Compiled app/views/taglibs/auto/admin/rapid/forms.dryml in 0.19s
Rendered controller: admin/agents; dryml-tag: index-page (1421.8ms)
<<<< Heroku did not finish this one which I believe calls the ones
before it.
Completed 200 OK in 3789.2ms (Views: 3577.2ms | ActiveRecord: 20.4ms)
It is rather hard do debug dryml on heroku, but I'll keep trying.
Don Ziesig
On 12/05/2013 01:05 PM, Donald Ziesig wrote:
Hi All!
I'm back!!!! :-( I hate to be a nuisance, but:
I have a new app that works fine locally under "foreman" in production
mode. It loads the front page in 1.6 seconds on a not-very-fast
laptop. I have been testing it on heroku as well and noticed that the
front page takes a significant amount of time to load (~25 seconds).
I set that aside as something to investigate later.
This past week I pushed a version with much more functionality to
heroku. Now, when I try to load the front page, heroku times out at
31 seconds. The heroku logs show that it is spending most of its time
compiling/rendering dryml and loading *all* of the internationalized
(no sign of 'en') versions of bootstrap-datepicker (they appear to be
being called from a hobo js file).
To be sure that my local server was not caching something I rebooted
the laptop and started the browser (empty) and the foreman server.
Nothing else was running on the laptop. I went to the local 'foreman'
server and it generated the front page with status:
Completed 200 OK in 1625.1ms (Views: 1271.2ms | ActiveRecord: 119.5ms)
It is now at the state where occasionally it will load the front page
from heroku before the timeout (1 out of 5-10 times).
After the front page loads, Heroku also takes a long time to load
other pages too (infrequently timing out at 31 seconds). The heroku
logs show that it is compiling/rendering dryml and trying to load the
international bootstrap datepickers for these pages as well. The
local version doesn't seem to do this and the other pages mostly load
in under a second.
It should be noted that I am NOT using any version of the bootstrap
datepickers in my app.
I am going to try a "warmup" page to see if I can get heroku to start
without timing out, then selecting the front page.
Again, I am soliciting help. This is a major business client who
needs the app as soon as possible. I can use a local server for a
while if I have to, but it has to be hosted professionally as the
ultimate deployment.
Thanks,
Don Ziesig
--
You received this message because you are subscribed to the Google
Groups "Hobo Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/groups/opt_out.
