Hey @deepakdinesh1123 — great stuff — let me have a read. I’m also looking at a couple of the loose-ends from this thread this week. Likely I’ll not get them all resolved, but it’s all good work, and will come in useful resolving the related tickets, over the next period.
Overall, I want to say, what a good job you’ve done all summer! Thank you for your effort. 
I hope you’ll continue to hang around with us, working on Django, and the benchmarks too.
You can always reach out to me if I can help you at all.
I will continue working on the template repository and channels load-testing project and I will also add some new request response benchmarks.
Super. Yep. 
I see you saw the thread about SQLite on Twitter — If you wanted to you could set up a locust project that made some reads, just to give a base load, and then slowly cranked up the number of writes until we hit the Database is locked error. Then adding a few different retry timeout values, to see the difference that makes. Finally enabling WAL for the same. (It’s on my list to add a note about enabling WAL to the docs (See #24018 (Support journal_mode=WAL for Sqlite) – Django) so there might be a small PR (just to the docs) available there too.
As I say, that’s all if you want to but it might be a bit of fun for this week? Up to you. 