akasamq / akasa Goto Github PK

Hi!

Recently I did many Profile-Guided Optimization (PGO) benchmarks on multiple projects (including many network-related projects like Envoy, HAProxy, etc.) - the results are available here. I think it could interesting to try to test PGO for optimizing the CPU part of Akasa.

I can suggest the following things to do:

• Evaluate PGO's applicability to Akasa.
• If PGO helps to achieve better performance - add a note to Akasa's documentation about that. In this case, users and maintainers will be aware of another optimization opportunity for Akasa.
• Provide PGO integration into the build scripts. It can help users and maintainers easily apply PGO for their own workloads.

Here are some examples of how PGO is already integrated into other projects' build scripts:

• Rustc: a CI script for the multi-stage build
• GCC:
  • Official docs, section "Building with profile feedback" (even AutoFDO build is supported)
  • A part in a "wonderful" configure script
• Clang: Docs
• Python:
  • CPython: README
  • Pyston: README
• Go: Bash script
• V8: Bazel flag
• ChakraCore: Scripts
• Chromium: Script
• Firefox: Docs
  • Thunderbird has PGO support too
• PHP - Makefile command and old Centminmod scripts
• MySQL: CMake script
• YugabyteDB: GitHub commit
• FoundationDB: Script
• Zstd: Makefile
• Foot: Scripts
• Windows Terminal: GitHub PR
• Pydantic-core: GitHub PR

After PGO, I can suggest evaluating LLVM BOLT as an additional optimization step after PGO.

For the Rust projects, I recommend starting with cargo-pgo.

I understand that the project is in the earliest stages of its lifecycle. So just think about the issue as a possible idea for improvements.

Hi，
The following error occurs when using websocket connection:

The configuration file is as follows:
`
listeners:
mqtt:
addr: 0.0.0.0:1883
proxy_mode: null
mqtts: null
ws:
addr: 0.0.0.0:8083
proxy_mode: null
wss: null
auth:
enable: false
password_file: test.yml
scram_users:
user:
hashed_password: 2a2a2a
iterations: 4096
salt: 73616c74
sasl_mechanisms:

• SCRAM-SHA-256
  check_v310_client_id_length: false
  shared_subscription_mode: Random
  max_allowed_qos: 2
  inflight_timeout: 15
  max_inflight_client: 10
  max_inflight_server: 10
  max_in_mem_pending_messages: 256
  max_in_db_pending_messages: 65536
  min_keep_alive: 10
  max_keep_alive: 65535
  multiple_subscription_id_in_publish: false
  max_session_expiry_interval: 4294967295
  max_packet_size_client: 268435460
  max_packet_size_server: 268435460
  topic_alias_max: 65535
  retain_available: true
  shared_subscription_available: true
  subscription_id_available: true
  wildcard_subscription_available: true
  hook:
  enable_before_connect: true
  enable_after_connect: true
  enable_publish: true
  enable_subscribe: true
  enable_unsubscribe: true
  `
  OS:
  Linux fan 6.1.0-13-amd64 Debian 6.1.55-1 (2023-09-29) x86_64 GNU/Linux