[jira] [Closed] (DISPATCH-448) Opening Dispatch Console webpage results in huge download (>5MiB)

["Ernest Allen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DISPATCH-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ernest Allen closed DISPATCH-448.
---------------------------------
    Resolution: Won't Fix

The overhead here is for the hawtio framework. Hawtio provides the environment to integrate multiple plugins into a single web application and needs to include all the underlying libraries that may be needed.

To mitigate this a custom could:
    - use the stand-alone version of the console
    - or if hawtio was a requirement for them, they could use a minimal version of the hawtio war file built from https://github.com/hawtio/hawtio
 

> 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.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org