knox-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep More (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KNOX-732) Knox does not recompress javascript resources
Date Thu, 15 Sep 2016 15:09:22 GMT

    [ https://issues.apache.org/jira/browse/KNOX-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15493591#comment-15493591
] 

Sandeep More commented on KNOX-732:
-----------------------------------

Results of some test I ran locally.
Setup, using VM (Ambari 2.4.0.0 ) and running Knox (0.9.1) locally.

The results are for the file app.js (compressed size 995 KB, decompressed size 7 MB) with
browser caching disabled.

Before KNOX-732 fix
 - Direct 442 ms 
 - Gateway 1.16 s

After KNOX-732 fix
 - Direct 442 ms 
 - Gateway 837 ms

These numbers should help us understand the relative improvement. YMMV.



> Knox does not recompress javascript resources
> ---------------------------------------------
>
>                 Key: KNOX-732
>                 URL: https://issues.apache.org/jira/browse/KNOX-732
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.9.1
>            Reporter: Sumit Gupta
>            Assignee: Sandeep More
>             Fix For: 0.10.0
>
>         Attachments: KNOX-732.001.patch, KNOX-732.002.patch, KNOX-732.003.patch, KNOX-732.004.patch,
Screen Shot 2016-09-10 at 2.41.25 PM.png
>
>
> When using the Ambari UI proxy service it is observed that the app.js file is about 7MB
whereas it is much smaller (about 1MB) when the UI is not proxied by Knox. 
> A compression solution needs to be investigated. Possibly by adding a gzip compression
handler or filter to jetty.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message