Connection‑reuse pool vs manual socket handling for love2d networking

Recommendation

Keep socket handling explicit in Love2D. Do not add a built-in connection-reuse pool to the framework. A small userland pool is acceptable only in your own game code when reconnect bursts are frequent and you can audit every close path. For timing, use love.timer.getTime() for reconnect intervals, not the delta passed to love.update.

Why explicit handling fits Love2D

Love2D exposes network sockets through LuaSocket-style objects without built-in pooling. That transparency matches the framework's explicit lifecycle philosophy: you create a socket, you use it, you close it. Hidden pool state makes it harder to see why file descriptors remain open during a crash or rapid reconnect cycle.

Socket exhaustion is usually caused by leaked handles or by opening sockets faster than the OS closes them, not by the absence of a pool. A pool reduces descriptor churn but can hide leaks and complicate debugging.

Confirmed facts versus likely explanation

Item	Status	Notes
Love2D networking has no built-in socket pool	Confirmed	Sockets are managed by the user or a binding.
OS file descriptor limit applies to every open socket	Confirmed	Check with ulimit -n.
love.timer.getTime() is higher resolution than frame delta	Confirmed	Suitable for frame-independent reconnect scheduling.
Intermittent exhaustion is caused by missing pool	Likely, not confirmed	More likely caused by unclosed sockets or reconnect bursts exceeding ulimit -n.

Steps for this case

1. Run ulimit -n to see the current file descriptor ceiling.
2. Wrap every socket creation in an explicit :close() in error and success paths.
3. Throttle reconnect attempts using love.timer.getTime() so retries are spaced by wall-clock seconds, not frame delta.
4. If profiling shows descriptor churn is still the bottleneck, add a small userland pool with a hard cap and mandatory cleanup on state changes.

local lastAttempt = 0
local RECONNECT_INTERVAL = 2.5

function love.update(dt)
  local now = love.timer.getTime()
  if needsReconnect and now - lastAttempt >= RECONNECT_INTERVAL then
    lastAttempt = now
    -- attempt socket creation and store handle
  end
end

Missing diagnostic detail

What is your ulimit -n value, and how many sockets are open simultaneously during a reconnect burst? This changes whether an explicit throttle is enough or whether a userland pool is required.

Assumptions and uncertainty

• Assumes Love2D 11.x with LuaSocket-style TCP objects.
• CPU cost of calling love.timer.getTime() once per reconnect check is negligible compared to socket I/O; no profile was run for this answer.
• Pool behavior under load is not verified by live testing.