#36293: Extend `django.utils.text.compress_sequence()` to optionally flush data
written to compressed file
-------------------------------+--------------------------------------
Reporter: huoyinghui | Owner: (none)
Type: New feature | Status: closed
Component: HTTP handling | Version: dev
Severity: Normal | Resolution: needsinfo
Keywords: gzip flush | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Jacob Walls):
> (The numbers as written have triple response time for ≈double response
size, unless I'm failing to read it right.)
Ah, I was comparing GZipMiddleware + Adam's proposal (859KB) to *no
GZIPMiddleware* (1.09MB), so it's about ~~10%~~ 22% smaller. (This was
because in #24242 the ask was "flushing makes the middleware useless in my
case", and I wanted to evaluate Adam's suggestion that that was a deviant
case.)
--
Ticket URL: <https://code.djangoproject.com/ticket/36293#comment:13>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/01070199f751b8ee-2283cf08-a468-4dec-a1ea-024652f59461-000000%40eu-central-1.amazonses.com.
