fix: increase max active requests and adjust debounce timing for conversation analysis

This commit is contained in:
MythEclipse
2026-05-18 06:04:30 +07:00
parent a037d17f53
commit 69ba7b497f
2 changed files with 26 additions and 3 deletions
+11 -2
View File
@@ -32,7 +32,7 @@ const conversationErrorCooldown = new Map<string, number>();
let activeRequests = 0;
let lastError: string | null = null;
const MAX_ACTIVE_REQUESTS = 1;
const MAX_ACTIVE_REQUESTS = 2;
const DEBOUNCE_MS = 1500;
const RECOVERY_INTERVAL_MS = 15000;
const ERROR_COOLDOWN_MS = 30000;
@@ -186,6 +186,10 @@ function scheduleConversationAnalysis(conversationKey: string): void {
clearTimeout(existingTimer);
}
// If we have available slots, process immediately with shorter debounce
const debounceTime =
activeRequests < MAX_ACTIVE_REQUESTS ? Math.min(DEBOUNCE_MS, 500) : DEBOUNCE_MS;
// Set new debounced timer
const timer = setTimeout(async () => {
conversationDebounceTimers.delete(conversationKey);
@@ -205,7 +209,7 @@ function scheduleConversationAnalysis(conversationKey: string): void {
if (messages.length > 0) {
await processBatch(conversationKey, messages);
}
}, DEBOUNCE_MS);
}, debounceTime);
conversationDebounceTimers.set(conversationKey, timer);
}
@@ -271,6 +275,11 @@ export function startPendingAIAnalysisWorker(): void {
const conversationKeys = await getPendingConversationKeys(100);
for (const key of conversationKeys) {
// Stop if we've reached max active requests
if (activeRequests >= MAX_ACTIVE_REQUESTS) {
break;
}
// Skip if already scheduled
if (conversationDebounceTimers.has(key)) {
continue;
+15 -1
View File
@@ -5,7 +5,10 @@ import {
getAnalysisQueueStatus,
queueMessageAnalysis,
} from "../moderation/aiAnalyzer";
import { getMessageById } from "../moderation/messageStore";
import {
getMessageById,
updateMessageAIAnalysis,
} from "../moderation/messageStore";
export function createAnalysisRoutes(): Router {
const router = express.Router();
@@ -35,6 +38,17 @@ export function createAnalysisRoutes(): Router {
throw new AppError("Message not found", "MESSAGE_NOT_FOUND", 404);
}
// Reset analysis status to pending so it gets picked up by the analyzer
await updateMessageAIAnalysis(id, {
status: "pending",
flags: null,
score: null,
raw: null,
analysis: null,
analyzedAt: null,
error: null,
});
// Queue for analysis
await queueMessageAnalysis(id);