Describe the bug We're using an application called "SendPortal" to

cURL Timeouts to postal via API about postal HOT 1 CLOSED

drraccoony commented on June 7, 2024

cURL Timeouts to postal via API

from postal.

Comments (1)

drraccoony commented on June 7, 2024

We identified and resolved the problem. Searching through closed issued, we found #2242.

We used this example and adjusted it to our needs,

require_relative '../lib/postal/config'
WEB_CONCURRENCY = 32
workers         32      # enables cluster mode
threads_count   = 128   # 1 worker per 128 threads
threads         threads_count, threads_count
bind_address    = Postal.config.web_server&.bind_address || '127.0.0.1'
bind_port       = Postal.config.web_server&.port&.to_i || ENV['PORT'] || 5000
bind            "tcp://#{bind_address}:#{bind_port}"
environment     Postal.config.rails&.environment || 'development'
prune_bundler
quiet           false
preload_app!

Though, we may change it to this to allow for Postal.config changes on the fly if needed:

require_relative '../lib/postal/config'

# Default values
default_web_concurrency = 32
default_threads_count = 128

# Use Postal.config values or defaults
WEB_CONCURRENCY = Postal.config.web_server&.web_concurrency || default_web_concurrency
workers         WEB_CONCURRENCY
threads_count   = Postal.config.web_server&.threads_count || default_threads_count
threads         threads_count, threads_count
bind_address    = Postal.config.web_server&.bind_address || '127.0.0.1'
bind_port       = Postal.config.web_server&.port&.to_i || ENV['PORT'] || 5000
bind            "tcp://#{bind_address}:#{bind_port}"
environment     Postal.config.rails&.environment || 'development'
prune_bundler
quiet           false
preload_app!

Reading more up on it, it appears It's redundant to set both WEB_CONCURRENCY and workers to the same value. Generally, WEB_CONCURRENCY is commonly used.

from postal.

Recommend Projects