[GH-ISSUE #478] Optimize server listing page: Parallelize SSH connection checks in afterReadHook #303

New issue

Closed

opened 2026-03-03 11:14:37 +03:00 by kerem · 2 comments

kerem commented

2026-03-03 11:14:37 +03:00

Owner

Originally created by @pavanbhaskardev on GitHub (Oct 14, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/478

Originally assigned to: @pavanbhaskardev on GitHub.

Problem

Currently, in the afterReadHook payload for the server listing page, SSH connection checks are performed sequentially for each server. If a user has multiple servers (e.g., 10), the system executes 10 SSH connection checks one after another, causing significant delays in updating the connection status.

Proposed Solution

Refactor the SSH connection checking logic in the afterReadHook to execute checks in parallel rather than sequentially.

Originally created by @pavanbhaskardev on GitHub (Oct 14, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/478 Originally assigned to: @pavanbhaskardev on GitHub. ### Problem Currently, in the `afterReadHook` payload for the server listing page, SSH connection checks are performed sequentially for each server. If a user has multiple servers (e.g., 10), the system executes 10 SSH connection checks one after another, causing significant delays in updating the connection status. ### Proposed Solution - Refactor the SSH connection checking logic in the `afterReadHook` to execute checks in parallel rather than sequentially.

kerem

2026-03-03 11:14:37 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-03-03 11:14:38 +03:00

Author

Owner

@pavanbhaskardev commented on GitHub (Oct 15, 2025):

We won't populate server details in afterRead hook
Instead we'll trigger a queue after every read of servers page which ssh and update server details
We'll add a redis flag to stop queue trigger in less than 2min

@pavanbhaskardev commented on GitHub (Oct 15, 2025): 1. We won't populate server details in `afterRead` hook 2. Instead we'll trigger a queue after every read of servers page which ssh and update server details 3. We'll add a redis flag to stop queue trigger in less than `2min`

kerem commented

2026-03-03 11:14:38 +03:00

Author

Owner

@pavanbhaskardev commented on GitHub (Oct 16, 2025):

Pushed changes to main: commit

@pavanbhaskardev commented on GitHub (Oct 16, 2025): Pushed changes to main: [commit](https://github.com/dflow-sh/dflow/commit/6e07270adad7a0b65026f71347fb9bf8f93a671e)