talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

Using HTML compression (gzip) and Tomcat

JM
Jesse Martinez
Mon, Apr 2, 2012 5:30 PM

Hi all,

I've been experimenting with turning on gzip compression on HTML
response packets for CSpace and have some overall good results.

In general, using compression for response packets decreases the
download time from server to client and helps to improve performance.
Using some rough, informal testing I was able to see compression
results from between 50% to 90% and a decreased load time of a
pre-cached login page of roughly 33%. (from 1.5s to 1.0 sec). Loading
a new Cataloging record page seemed speedier too from my informal
testing.

My notes can be found here:
http://issues.collectionspace.org/browse/CSPACE-4998

  • Jesse
Hi all, I've been experimenting with turning on gzip compression on HTML response packets for CSpace and have some overall good results. In general, using compression for response packets decreases the download time from server to client and helps to improve performance. Using some rough, informal testing I was able to see compression results from between 50% to 90% and a decreased load time of a pre-cached login page of roughly 33%. (from 1.5s to 1.0 sec). Loading a new Cataloging record page seemed speedier too from my informal testing. My notes can be found here: http://issues.collectionspace.org/browse/CSPACE-4998 - Jesse
AR
Aron Roberts
Mon, Apr 2, 2012 6:05 PM

Many thanks for initiating this investigation, Jesse, and your detailed notes!

These notes, in CSPACE-4998, are now referenced from this landing
page document:

http://wiki.collectionspace.org/display/UNRELEASED/Tuning+CollectionSpace+for+Performance

Aron

On Mon, Apr 2, 2012 at 10:30 AM, Jesse Martinez
jmartinez@movingimage.us wrote:

Hi all,

I've been experimenting with turning on gzip compression on HTML
response packets for CSpace and have some overall good results.

In general, using compression for response packets decreases the
download time from server to client and helps to improve performance.
Using some rough, informal testing I was able to see compression
results from between 50% to 90% and a decreased load time of a
pre-cached login page of roughly 33%. (from 1.5s to 1.0 sec). Loading
a new Cataloging record page seemed speedier too from my informal
testing.

My notes can be found here:
http://issues.collectionspace.org/browse/CSPACE-4998

 - Jesse


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Many thanks for initiating this investigation, Jesse, and your detailed notes! These notes, in CSPACE-4998, are now referenced from this landing page document: http://wiki.collectionspace.org/display/UNRELEASED/Tuning+CollectionSpace+for+Performance Aron On Mon, Apr 2, 2012 at 10:30 AM, Jesse Martinez <jmartinez@movingimage.us> wrote: > Hi all, > > I've been experimenting with turning on gzip compression on HTML > response packets for CSpace and have some overall good results. > > In general, using compression for response packets decreases the > download time from server to client and helps to improve performance. > Using some rough, informal testing I was able to see compression > results from between 50% to 90% and a decreased load time of a > pre-cached login page of roughly 33%. (from 1.5s to 1.0 sec). Loading > a new Cataloging record page seemed speedier too from my informal > testing. > > My notes can be found here: > http://issues.collectionspace.org/browse/CSPACE-4998 > >  - Jesse > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org