You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bifromq.apache.org by "visoar (via GitHub)" <gi...@apache.org> on 2026/08/12 13:20:53 UTC

[I] [Content] Publish a Linux tuning guide for high-concurrency MQTT workloads [bifromq-sites]

visoar opened a new issue, #72:
URL: https://github.com/apache/bifromq-sites/issues/72

   Part of #66.
   
   ## Opportunity
   
   Third-party modeled traffic data identifies `nf_conntrack_max max value` (estimated monthly volume 430) and `nf_conntrack_max` (220) as the leading non-brand keywords associated with the Apache hostname. The current repository already has an OS tuning page, but BifroMQ did not appear in the tested first Google result page for `nf_conntrack_max max value`.
   
   This is a strong product/content fit: operators running high-connection MQTT workloads need connection-tracking, socket, file-descriptor, backlog, and memory guidance that generic Linux answers do not provide.
   
   ## Proposed content
   
   Upgrade `/docs/admin_guide/tuning/os_tuning_linux/` into a practical, versioned guide for BifroMQ operators:
   
   - Symptoms and diagnostics for `nf_conntrack: table full`.
   - How to inspect `nf_conntrack_count`, `nf_conntrack_max`, and buckets.
   - A capacity-sizing method tied to expected MQTT TCP connections, NAT topology, memory, and safety margin.
   - Persistent configuration examples for common Linux distributions and Kubernetes nodes.
   - Related socket backlog, ephemeral port, file descriptor, TCP keepalive, and TIME_WAIT considerations.
   - Clear cautions against blindly copying a maximum value.
   - Reproducible load-test/benchmark evidence and links to BifroMQ observability metrics.
   - FAQ sections matching related searches such as default value, Ubuntu behavior, and table-full recovery.
   
   ## Internal linking
   
   Link from installation, Kubernetes deployment, high availability, observability, and benchmark pages; link back to the relevant configuration and metrics references.
   
   ## Acceptance criteria
   
   - [ ] The page has a concise query-aligned title and description.
   - [ ] Recommendations distinguish kernel facts from BifroMQ-specific guidance and cite authoritative Linux/kernel sources.
   - [ ] Commands are tested and include rollback/safety notes.
   - [ ] The page is linked from at least four relevant documentation routes.
   - [ ] After indexing, track GSC impressions/position for the target cluster and on-site engagement over two complete 28-day periods.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Docs] Improve Linux tuning guidance for high-concurrency MQTT workloads [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar commented on issue #72:
URL: https://github.com/apache/bifromq-sites/issues/72#issuecomment-5268248248

   Updated after an ASF-specific policy review: the scope now prioritizes public dev-list governance, Incubator/brand compliance, ASF privacy rules, vendor neutrality, and user/community outcomes. External third-party tracking and SEO link-building are explicitly out of scope.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Docs] Improve Linux tuning guidance for high-concurrency MQTT workloads [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar commented on issue #72:
URL: https://github.com/apache/bifromq-sites/issues/72#issuecomment-5371533034

   Implementation is ready for review in #86.
   
   The change replaces fixed and outdated kernel recommendations with measurement-led sizing, rollback, upstream kernel/Kubernetes references, and reproducible validation across conntrack, file descriptors, queues, ports, TCP behaviour, and Kubernetes nodes. `pnpm run check:site`, `pnpm run typecheck`, and CI all pass.
   
   @yonny has been asked to review the technical guidance, with the reason for the change and the highest-risk areas called out in the PR. Keep this issue open until that review is complete and the post-publication measurement item is recorded.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Content] Publish a Linux tuning guide for high-concurrency MQTT workloads [bifromq-sites]

Posted by "visoar (via GitHub)" <gi...@apache.org>.
visoar commented on issue #72:
URL: https://github.com/apache/bifromq-sites/issues/72#issuecomment-5267381417

   Dependency: post-publication measurement requires the canonical-host setup in #67.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@bifromq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org