11–20 of 60 posts
Looks like Django 6 is getting an offical task system. There’s no real world brokers or workers supported (at least built in), but still centralising around a standard interface might make things nicer than the celery tentacle monsters Django apps eventually tend to mutate into.
Looks like Django 6 is getting an offical task system. There’s no real world brokers or workers supported (at least built in), but still centralising around a standard interface might make things nicer than the celery tentacle monsters Django apps eventually tend to mutate into.
I don´t understand how you could use this new tasks system in production if there is no real workers when it's released? Are there any 3rd party yet?
At leas that's my guess.
Love me Django and excited about this release. It’s been quite a journey through the years. I started working with it a little before 1.0 and continue to do so. Nowadays as an independent consultant which gives me the ability to really help keep Django systems up to date. Yes, there’s some rough edges. Like updating can be tricky sometimes, and performance relating to DB queries is a skill in itself, but in general i…
Looks like Django 6 is getting an offical task system. There’s no real world brokers or workers supported (at least built in), but still centralising around a standard interface might make things nicer than the celery tentacle monsters Django apps eventually tend to mutate into.
I don´t understand how you could use this new tasks system in production if there is no real workers when it's released? Are there any 3rd party yet?
But if you want to schedule a task further in the future, then a new backend will be needed for that.
I love Django, and the new `tasks` framework to replace `celery` (/whatever processor you prefer) looks great. I've only recently come back to it, and I do hope they continue to add more batteries to their "batteries included" framework over time. I was surprised just how much stuff I had to add to my little project that will require updating _outside_ the main framework, eg.: * django-components for little template…
I just recently found it and it has been amazing. It logs all your requests and responses by default (but is quite configurable) as well as your SQL queries (and how many/how long they take), in an easily searchable database. It can even profile functions for you.
Makes it very to see at a glance what pages are slow for people, and why, so they can be optimized accordingly.
Earlier quoted context omitted.
I don´t understand how you could use this new tasks system in production if there is no real workers when it's released? Are there any 3rd party yet?
My understanding is that if you just need to return a response to the client as quickly as possible, but are ok with then processing your task directly after that, then it's still usable today. But if you want to schedule a task further in the future, then a new backend will be needed for that.
Love me Django and excited about this release. It’s been quite a journey through the years. I started working with it a little before 1.0 and continue to do so. Nowadays as an independent consultant which gives me the ability to really help keep Django systems up to date. Yes, there’s some rough edges. Like updating can be tricky sometimes, and performance relating to DB queries is a skill in itself, but in general i…
What're some DB query performance issues you've run across in the past and how did you resolve them?