django-debug-toolbar VS template-benchmarks-rs

The reason behind this splitting is that we can safely use packages and related settings only where we need. For example, this starter kit has the package django-debug-toolbar. This is only intended for your development environment and not for your production. This can be very risky if used in production because if your Django project encounters errors, all the debug info will be shown to the user which is a severe security risk. Similarly, for tracking errors in production, we're using Sentry which is not needed in our local environment since we already have django-debug-toolbar. For keeping these settings file separate so that they don't conflict with each other, the settings file is split for serving different environments.

django-debug-toolbar: https://github.com/jazzband/django-debug-toolbar

https://github.com/jazzband/django-debug-toolbar/issues?q=is%3Aopen+is%3Aissue+label%3ABug

https://github.com/jazzband/django-debug-toolbar Allows you to check which sql queries are being run on your app. See if they are optimized first.

Perhaps try the django-debug-toolbar. It might be able to tell you what is causing the slow load time.

I would start with https://github.com/jazzband/django-debug-toolbar and figure out what causes the slowness.

-> The debugging above from django-debug-toolbar

Documentation, including installation and configuration instructions, is available at https://django-debug-toolbar.readthedocs.io/.

Any recommendations for rust template engines? I'd like something that can easily render labeled fragments of a template instead of requiring me to split a page into a dozen little files. Kinda like inline {{block}} definitions in Go's html/template. Speed is also nice.

From template-benchmark-rs [0] I found sailfish [1] (fast, but no fragments(?)). render-rs [2] and syn-rsx [3] (2022) both let you write html in rust macros which is cool (maybe that can substitute for fragments?). Then there's gtmpl-rust [4] which is just Go templates reimplemented in rust.

[0]: https://github.com/rosetta-rs/template-benchmarks-rs

[1]: https://github.com/rust-sailfish/sailfish

[2]: https://github.com/render-rs/render.rs last updated Jul 2020

[3]: https://github.com/stoically/syn-rsx last updated Nov 2022

[4]: https://github.com/fiji-flo/gtmpl-rust

Personally, I'd recommend Maud if you don't need something with runtime reloading. Not only is it much faster, it implements a template language that is effectively the Rust-syntax equivalent to Slim or Haml using a procedural macro, so you get compile-time verification that your HTML output is well-formed.

I've been maintaining several benchmark repos based off of template-benchmarks-rs. I've noticed there are several other benchmark repos that are hard to know about.

I'm tempted to collect all of these benchmark repos into a github org to make them easier to find. So far I know of parser, md, argparse, and template languages.

Simple and straightforward. The only thing I'd change personally is using sailfish over markup. Seems to be the fastest templating engine?

As I said in my other post, runtime performance wasn't a concern for me except to catch anything egregious, like mini_markdown hanging. If people want to expand on this with different representative cases and criterion like template-benchmarks-rs, they are welcome to!

That's why I use Sailfish for server-side templating in my Rust web projects. It's ridiculously fast.

As for templating, here's a benchmark that can double as a list of candidates to choose from... though, again, Rust stuff tends to be fast, so don't assume that the slowest templating engine on a Rust-vs-Rust benchmark is going to be slow.

Yeah. You're much better off worrying about template rendering performance or database query optimization than the framework itself.