#36520: Performance Regression in parse_header_params
---------------------------------+------------------------------------
     Reporter:  David Smith      |                    Owner:  (none)
         Type:  Bug              |                   Status:  new
    Component:  HTTP handling    |                  Version:  dev
     Severity:  Release blocker  |               Resolution:
     Keywords:                   |             Triage Stage:  Accepted
    Has patch:  0                |      Needs documentation:  0
  Needs tests:  0                |  Patch needs improvement:  0
Easy pickings:  0                |                    UI/UX:  0
---------------------------------+------------------------------------
Comment (by Jake Howard):

 That sounds sensible to me.

 As an aside, the parsing implementations from
 
[https://github.com/psf/requests/blob/4b9c546aa3f35fca6ca24945376fe7462bb007c4/src/requests/utils.py#L504
 requests] and
 
[https://github.com/overdosyu/werkzeug/blob/19a4a145f68535ad533d5a34bfad8474c87c54e2/werkzeug/http.py#L318
 werkzeug] (ie `flask`) are both hand-rolled, and differ a fair bit from
 Django's. It's possibly using those implementations may be faster (or at
 least be used to accelerate what Django already has).

 I'd be interested to see how those benchmark against `cgi` and
 `email.message`.
-- 
Ticket URL: <https://code.djangoproject.com/ticket/36520#comment:14>
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/010701985a834a40-571e9c4a-6a3f-47fa-a7ca-8e8de5366388-000000%40eu-central-1.amazonses.com.

Reply via email to