DaemonSnake
Hello,
We were having some issue with Oban Pro (1.4.2) in our AWS production environment (Aurora PG 16.1).
Pretty often during the day the following oban-internal query would takes the first place
in the performance analysis view in AWS with around:
- 3+ AAS,
- ~3s+ average latency
- +1 call/s.
The query goes as follow:
SELECT o0."state", o0."scheduled_at" FROM "public"."oban_jobs" AS o0 WHERE (o0."meta" @> $1) AND (o0."state" != 'completed') AND (o0."id" < $2) ORDER BY o0."id" DESC LIMIT 1
We realized that we had many scheduled jobs that had been cancelled (around 200k) and were not getting pruned.
We decided to delete them and the above now well-behaves.
We believe it was caused by state != 'completed'.
What is the purpose of that query and why is ‘completed’ the only state that is excluded ?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Enabling companies to succeed by building software people love.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Practical resources that improve the lives of professional developers.
Develop your skills with books, videos, and courses.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 2- Show Best Posts
- Show All Posts (oldest first)
- Show All Posts (newest first)
sorenone
Welcome, @DaemonSnake! Thank you for bringing your question to the forum.
Definitely upgrade. There are major bug fixes and performance improvements.
How did you cancel those jobs? What is your pruning config? Cancelled jobs are normally prunable.
Are you using
chainsorworkflows? That’s going to help us narrow it down.DaemonSnake
Thanks for you quick reply @sorenone
Thanks for the info, done ^^
indeed we are seing a bunch of performance improvements
We used
Oban.cancel_all_jobs, but those jobs had schedule_at dates far into the future.We are using the Chunk worker