Changes between Version 3 and Version 4 of SummerOfCode2022

Timestamp:

Feb 9, 2022, 10:05:37 AM (4 years ago)

Author:

Carlton Gibson

Comment:

--

SummerOfCode2022

@@ -142 +142 @@
 Carrying-on and extending that work would be a great addition. 
 
+== Django Benchmarking ==
+
+https://github.com/django/djangobench
+
+Django has had a benchmarking suite for a while, but we've generally gotten more
+slack at tracking the effects each commit and release has. We should institute
+a set of top-level benchmarks aimed at various areas (the current set in
+`djangobench` are weak in, say, the HTTP-serving-speed area) and then run them
+against pull requests and each release, so we can make sure Django doesn't get
+slower while nobody is looking.
+
+Recent work has gone into [https://github.com/django/djangobench/issues/38
+running the benchmarks regularly and integrating the Airspeed Velocity (ASV)
+package]. The task would be to help pick-up that work and bring the
+benchmarking up to the next level.
+
+There's particular work in benchmarking the efforts to bring async to Django. 
+It would be great to be able to see the effects of using ASGI (vs WSGI say), and 
+of particular suggested changes (such as [https://code.djangoproject.com/ticket/32172 making signals async aware]). 
+The [https://github.com/django/channels/tree/main/loadtesting Channels project also has benchmarks that need updating].
+
+Creating a test harness using (say) [https://locust.io Locust.io] would make a great project. 
+
 ... MORE IDEAS INCOMING ... 
-
 
 == Or Create Your Own ==