You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Jiri Danek (JIRA)" <ji...@apache.org> on 2016/07/19 15:46:20 UTC
[jira] [Created] (DISPATCH-448) Opening Dispatch Console webpage
results in huge download (>5MiB)
Jiri Danek created DISPATCH-448:
-----------------------------------
Summary: Opening Dispatch Console webpage results in huge download (>5MiB)
Key: DISPATCH-448
URL: https://issues.apache.org/jira/browse/DISPATCH-448
Project: Qpid Dispatch
Issue Type: Bug
Components: Console
Reporter: Jiri Danek
1. Open debugging console in browser (Ctrl+Shift+C in Chromium).
2 . Switch to the Network tab.
3. Open the console, 10.0.2.2:8080/hawtio/dispatch_router, and wait for it to load
The console reports 5.1 MiB of data transferred. I think this is just too much. The Dispatch bits are actually small, most of it is Hawt.io.
I am using dispatch-console from this docker image https://hub.docker.com/r/jdanekrh/dispatch-console/, with Hawt.io version 1.4.65, the "hawtio-default" release.
* The biggest offender is the app.js, 2.7 MiB. There was upstream issue to decrease the size, but it went nowhere. https://github.com/hawtio/hawtio/issues/1373
* Then there is the image /hawtio/img/icons/java.svg, 813 KiB and it is not even being displayed. Kill it, please.
FYI, rhea.js is just 115 KiB
This issue affects users accessing the console over slower connections fir the first time (before resources get cached). It also affects automated regression testing, because every test is (ideally) executed with a clean browser profile and filling the cache takes time.
This issue would likely require working with Hawt.io to resolve.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org