Martin Brennan 24ec06ff85 FEATURE: Reintroduce better thread reply counter cache (#21197) ... This was reverted in 38cebd3ed5. The issue was that I was using Discourse.redis.delete_prefixed which does a slow redis KEYS lookup, which is not advised in production. This commit removes that, and also ensures the periodical thread count update only happens if threading is enabled. I changed to use a redis INCR/DECR for reply count cache. This avoids a round trip to redis to GET the current count, and also avoids multi-process issues, where if there's two processes trying to increment at the same time, they may both receive the same value, add one to it, then both write the same value back. Then, it's only n+1 instead of n+2. This also prevents almost all chat scheduled jobs from running if chat is disabled, the only one remaining is the message retention job.		2023-04-24 09:32:04 +10:00
..
action	FEATURE: Mark all chat channels read with a shortcut (#20629)	2023-03-22 13:24:07 +10:00
auto_remove
create_category_channel.rb	DEV: Move channel creation for category into service (#21167)	2023-04-24 09:15:16 +10:00
lookup_thread.rb
mark_all_user_channels_read.rb	FIX: Do not count thread messages for channel unreads (#21126)	2023-04-19 08:53:51 +10:00
message_destroyer.rb	FIX: Trashing message should reset last read (#20912)	2023-04-04 09:30:38 +10:00
publisher.rb	FEATURE: Reintroduce better thread reply counter cache (#21197)	2023-04-24 09:32:04 +10:00
restore_message.rb	FEATURE: Reintroduce better thread reply counter cache (#21197)	2023-04-24 09:32:04 +10:00
trash_channel.rb
trash_message.rb	FEATURE: Reintroduce better thread reply counter cache (#21197)	2023-04-24 09:32:04 +10:00
update_channel_status.rb
update_channel.rb
update_user_last_read.rb	FEATURE: Mark all chat channels read with a shortcut (#20629)	2023-03-22 13:24:07 +10:00