boostorg / boostorg/beast

Websocket over SSL is very slow to compile

Open
#2,975 1 comment 1 reaction 0 assignees View on GitHub
Dominant language
C++
Stars
4.8k
Forks
694
Avg merge
12h 48m
Merged PRs (30d)
1

Description

I'm writing and HTTPS server with WSS support. I've noticed that it's extremely slow to compile and generates a very bloated binary.
I've tried #including only what I need from both Asio and Beast but that makes no difference.
HTTPS on its own is fine. HTTP + WS is fine. But HTTPS + WSS is mega slow to compile (like 30s to compile a single file)
Anybody noticed this before?
@vinniefalco what's the state of https://github.com/cppalliance/http_proto and https://github.com/cppalliance/ws_proto ?
I imagine you eventually want to replace Beast with your suite of "sans-io" libraries that sit on top of Asio right?

Contributor guide

Open the contributing guide

Research direction

The report names no files, tests, or minimal reproduction. Start by reproducing the HTTPS+WSS build described, comparing it with HTTPS-only and HTTP+WS, then inspect the Beast and Asio includes and the referenced http_proto and ws_proto projects. Done requires a confirmed explanation or actionable fix for the compile-time and binary-size regression.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
networking, performance
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.