The last time I tested this, gzip'ing didn't really make much of a
difference.
Essentially we had this block repeated 500 times:
<div>
<div>
something here
</div>
<input some really long stuff here>
<div>
</div>
This was then also indented 4x5 places from the left, so the amount of
white space was massive.
Some browsers (such as Chrome) handled it fine, but IE8/IE9 lagged pretty
badly.
Feel free to test for yourself, but this was certainly our experiences from
it.
Cal
On Fri, Jul 6, 2012 at 3:36 PM, Russell Keith-Magee <[email protected]
> wrote:
> On Fri, Jul 6, 2012 at 10:29 PM, Cal Leeming [Simplicity Media Ltd]
> <[email protected]> wrote:
> > -1 on removing spaceless.
> >
> > On pages where you have lots of rows in a loop, the amount of whitespace
> you
> > end up with can massively increase page loading times.
>
> You did read my comment about using GZip compression, right? GZip is
> *really* good at compressing sequences of identical characters. I'd be
> deeply surprised if the effect of introducing large blocks of
> whitespace into a GZip compressed HTML stream was any more than a
> rounding error. It should also be *much* more effective, and involve
> less computational load, than the effect of running a regex over your
> page to extract whitespace (which is all spaceless is doing).
>
> Yours,
> Russ Magee %-)
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected].
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en.
