nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

anybody ever tried to enable mod_deflate?

RonaldV

Hi,

did anybody ever try to install and enable mod_deflate (= gzip compression module for apache2) for the apache-server that comes with Teamsite?

I could imagine that is could give a performance boost specially when working from a remote location. And it is often cheaper to add extra cpu-power to a server then to upgrade the network.

Ronald

Find more posts tagged with

Comments

jed

Hi,

did anybody ever try to install and enable mod_deflate (= gzip compression module for apache2) for the apache-server that comes with Teamsite?

I could imagine that is could give a performance boost specially when working from a remote location. And it is often cheaper to add extra cpu-power to a server then to upgrade the network.

Ronald

It might be easier [and upgrade proof] to put a proxy in front of TeamSite that will handle things like compression. For example, you can configure Sun Webserver 7 with a reverse proxy back to the TeamSite GUI. If you enable compression on webserver 7, it will compress all the content before it is sent to the client.

In theory, this could be setup in about an hour. Adding a module to iw-webd--uff!

jed

In theory, this could be setup in about an hour. Adding a module to iw-webd--uff!

OK..so it only takes ~30 minutes to setup Smiley Happy

I was able to:
- install and enable ws7 listening on port 443 w/ a self signed cert (very easy to setup ssl)
- pass all requests back to the TeamSite GUI on port 80 via reverse proxy
- add gzip compression (level 6) on all text and javascript requests

https://star-dev.sfbay.sun.com/iw-cc/base/widget/pagination/pagination.js

GET /iw-cc/base/widget/pagination/pagination.js HTTP/1.1

[...]

HTTP/1.x 200 OK

Server: Sun-Java-System-Web-Server/7.0

[...]
Content-Type: application/x-javascript

Via: 1.1 https-star-dev

Proxy-agent: Sun-Java-System-Web-Server/7.0

Content-Encoding: gzip

Vary: accept-encoding

Transfer-Encoding: chunked

If I get a moment, I can do some benchmarks between a compressed and non-compressed request.

jed

If I get a moment, I can do some benchmarks between a compressed and non-compressed request.

It is slightly faster. When loading the main TeamSite UI (/iw-cc/command/iw.ccpro.filesys) with a shift-reload, firebug reports my load times as:

proxied via WS7: https + compression[9]
2.67
2.75
2.84

proxied via WS7: http + compression[9]
2.7
2.61
2.61

Native TeamSite GUI http
3.4
3.37
3.05

I am not the prime test case for this as I am 10 feet from the datacenter. Compression will benefit those further away. Also, the server only has 1350mhz CPU's. A higher clock rate should improve results as it will compress the content faster. In theory, I could install the webserver to an x86 box with much faster CPU's if I really wanted to.

mdang

Recent releases of TeamSite (6.7.2 for sure) enables mod_deflate OOTB.

RonaldV

Recent releases of TeamSite (6.7.2 for sure) enables mod_deflate OOTB.

Yes, you are right. Our 672 box returns this in the header:

Content-Encoding: gzip

That's good news. Such a simple trick to gain some extra speed!