RequestHunt is a community-driven platform that collects and curates feature requests from X (Twitter), Reddit, and GitHub. We help product teams discover what features real users are asking for, making it easier to validate product ideas and prioritize feature development based on actual user demand.

How does RequestHunt collect feature requests?

RequestHunt uses AI-powered extraction to automatically collect feature requests from social media platforms including X, Reddit, and GitHub. The platform monitors discussions, issues, and posts to identify genuine user feature requests, extracting key information like the requested feature, product mentioned, and user sentiment.

Who uses RequestHunt?

RequestHunt is used by product managers, founders, developers, and product teams who want to discover what features real users are requesting. It's particularly valuable for startups looking to validate ideas, established companies prioritizing their roadmap, and developers building products that solve real user problems.

Is RequestHunt free to use?

Yes, browsing and searching feature requests on RequestHunt is completely free. We also offer API access for developers who want to integrate feature request data into their own applications. Check our pricing page for API plan details.

How often is RequestHunt data updated?

RequestHunt continuously collects feature requests from Reddit, X (Twitter), GitHub, YouTube, LinkedIn, and Amazon. You can also trigger on-demand scraping via the API or web interface to get the freshest data for any topic.

[Kubeflow] Support Multi-Node NVLink (MNNVL) for TrainJob with Topology Aware Scheduling

Enable high-bandwidth GPU-to-GPU communication across nodes connected via NVSwitch fabric by adding support for automatic compute domain creation for TrainJob pods, improving performance for distributed training workloads.

Original Source

@@Ronkahn21 | 3 pts | 3/1/2026

Multi-Node NVLink (MNNVL) enables high-bandwidth GPU-to-GPU communication across nodes connected via NVSwitch fabric. For distributed training workloads to achieve best performance, all TrainJob pods should be placed on nodes within the same MNNVL domain. Currently, users must manually create the compute domain CRD to leverage IMEX channels and manually configure placement constraints for their workloads. This doesn't scale. We should add support for: 1. **Automatic compute domain creation** — Trainer should automatically create the compute domain CRD required for MNNVL and IMEX channel configuration, removing the manual setup burden from users. 2. **Topology Aware Scheduling (TAS) integration** — Use [TAS](https://kueue.sigs.k8s.io/docs/concepts/topology_aware_scheduling/) to ensure best placement of TrainJob pods within MNNVL domains. /kind feature /area controller CC @andreyvelich

Discussion

Loading comments...