Try improving Ahoy geocoding behavior

This commit is contained in:
Zach Latta
2025-05-08 20:54:02 -04:00
parent 797334d08b
commit 9f4ccfe519
3 changed files with 2 additions and 6 deletions

View File

@@ -9,4 +9,4 @@ Ahoy.api = false
# see https://github.com/ankane/ahoy#geocoding
Ahoy.geocode = true
Ahoy.job_queue = :ahoy
Ahoy.job_queue = :literally_whenever

View File

@@ -1,4 +0,0 @@
# Override Ahoy::GeocodeV2Job priority to be low
Ahoy::GeocodeV2Job.class_eval do
self.priority = 1000
end

View File

@@ -8,7 +8,7 @@ Rails.application.configure do
config.good_job.execution_mode = :async
# https://github.com/bensheldon/good_job#configuring-your-queues
config.good_job.queues = "real_time:2; latency_10s:8; latency_1m:2; *:1"
config.good_job.queues = "real_time:2; latency_10s:8; latency_1m:2; latency_5m:1 literally_whenever:1 *:1"
# https://github.com/bensheldon/good_job#pgbouncer-compatibility
GoodJob.active_record_parent_class = "ApplicationDirectRecord"