Farhan Ali RazaMar 9

Over the last few weeks, I focused on removing overhead from the request hot path in Django Bolt. The results from v0.6.4 → v0.7.0 are honestly better than I expected. I remember when I put 60k RPS in GitHub README because that was the maximum I was able to get from this. Now the same endpoint under the same condition achieves 160k RPS.

github.com/dj-bolt/django-bolt

Here is how I did it.

Show threadPaolo Melchiorre

Hey @farhanaliraza great job on this new release of Django Bolt.👏

I suggest everyone to try it. 👍

#Django #DjangoBolt #Rust #Python

Mar 10 at 10:40pmWeb
Show threadFarhan Ali RazaMar 10
@paulox Thank you. Excited for it now.
Show threadPaolo MelchiorreMar 10
@farhanaliraza I have just one question why not just use granian instead of the http server extra code?
Show threadFarhan Ali RazaMar 10

@paulox For the asgi mount part ?
I tried using it but the granian code is coupled together. It can be by making granian a dependency. But it will still conflict because I have configuration for actix server for the main API part and granian for the asgi part .

So I just implemented bad version of granian 😅

Show thread?Syntax ErrorMar 11
@paulox @farhanaliraza this is super timely as I just began a new Django api personal project, can't wait to try it out
Show threadFarhan Ali RazaMar 11
@moondog8 @paulox Great. Let me know of your experience.