Skip to main content

Deploying DeepSeek on 96 H100 GPUs

·460 words·3 mins
Hacker News Tech
Articoli Interessanti - This article is part of a series.
Part : Everything as Code: How We Manage Our Company In One Monorepo At Kasava, we've embraced the concept of "everything as code" to streamline our operations and ensure consistency across our projects. This approach allows us to manage our entire company within a single monorepo, providing a unified source of truth for all our configurations, infrastructure, and applications. **Why a Monorepo?** A monorepo offers several advantages: 1. **Unified Configuration**: All our settings, from development environments to production, are stored in one place. This makes it easier to maintain consistency and reduces the risk of configuration drift. 2. **Simplified Dependency Management**: With all our code in one repository, managing dependencies becomes more straightforward. We can easily track which versions of libraries and tools are being used across different projects. 3. **Enhanced Collaboration**: A single repository fosters better collaboration among team members. Everyone has access to the same codebase, making it easier to share knowledge and work together on projects. 4. **Consistent Build and Deployment Processes**: By standardizing our build and deployment processes, we ensure that all our applications follow the same best practices. This leads to more reliable and predictable deployments. **Our Monorepo Structure** Our monorepo is organized into several key directories: - **/config**: Contains all configuration files for various environments, including development, staging, and production. - **/infrastructure**: Houses the infrastructure as code (IaC) scripts for provisioning and managing our cloud resources. - **/apps**: Includes all our applications, both internal tools and customer-facing products. - **/lib**: Stores reusable libraries and modules that can be shared across different projects. - **/scripts**: Contains utility scripts for automating various tasks, such as data migrations and backups. **Tools and Technologies** To manage our monorepo effectively, we use a combination of tools and technologies: - **Version Control**: Git is our primary version control system, and we use GitHub for hosting our repositories. - **Continuous Integration/Continuous Deployment (CI/CD)**: We employ Jenkins for automating our build, test, and deployment processes. - **Infrastructure as Code (IaC)**: Terraform is our tool of choice for managing cloud infrastructure. - **Configuration Management**: Ansible is used for configuring and managing our servers and applications. - **Monitoring and Logging**: We use Prometheus and Grafana for monitoring,
Part : This Article
Featured image
#### Source

Type: Hacker News Discussion Original link: https://news.ycombinator.com/item?id=45064329 Publication date: 2025-08-29

Author: GabrielBianconi


Summary
#

WHAT
#

DeepSeek is an open-source large language model known for its high performance. Its unique architecture, based on Multi-head Latent Attention (MLA) and Mixture of Experts (MoE), requires an advanced system for efficient large-scale inference.

WHY
#

DeepSeek is relevant for AI business because it offers high performance at a lower cost compared to commercial solutions. Its open-source implementation allows for significant reduction in operational costs and improvement in inference efficiency.

WHO
#

Key players include the SGLang team, which developed the implementation, and the open-source community that can benefit from and contribute to the model’s improvements.

WHERE
#

DeepSeek positions itself in the market of open-source AI solutions, offering a competitive alternative to proprietary solutions. It is primarily used in advanced cloud environments, such as the Atlas Cloud.

WHEN
#

DeepSeek is an established model, but its optimized implementation is recent. The temporal trend shows a growing interest in performance optimization and reduction of operational costs.

BUSINESS IMPACT
#

  • Opportunities: Reduction of operational costs for large language model inference, performance improvement, and scalability.
  • Risks: Competition with proprietary solutions that may offer more advanced support and integrations.
  • Integration: Possible integration with the existing stack to improve inference operation efficiency.

TECHNICAL SUMMARY
#

  • Core technology stack: Uses prefill-decode disaggregation and large-scale expert parallelism (EP), supported by frameworks such as DeepEP, DeepGEMM, and EPLB.
  • Scalability: Implemented on 96 H100 GPUs, achieving a throughput of .k input tokens per second and .k output tokens per second per node.
  • Technical differentiators: Performance optimization and reduction of operational costs compared to commercial solutions.

HACKER NEWS DISCUSSION
#

The discussion on Hacker News mainly highlighted topics related to the optimization and performance of DeepSeek’s implementation. The community appreciated the technical approach adopted to improve large-scale inference efficiency. The main themes that emerged were performance optimization, technical implementation, and system scalability. The overall sentiment is positive, with recognition of DeepSeek’s potential to reduce operational costs and improve inference operation efficiency.


Use Cases
#

  • Private AI Stack: Integration into proprietary pipelines
  • Client Solutions: Implementation for client projects
  • Strategic Intelligence: Input for technological roadmap
  • Competitive Analysis: Monitoring AI ecosystem

Third-Party Feedback
#

Community feedback: The HackerNews community commented with a focus on optimization, performance (9 comments).

Full discussion


Resources
#

Original Links #


Article suggested and selected by the Human Technology eXcellence team, processed through artificial intelligence (in this case with LLM HTX-EU-Mistral3.1Small) on 2025-09-04 18:56 Original source: https://news.ycombinator.com/item?id=45064329

Related Articles #

Articoli Interessanti - This article is part of a series.
Part : Everything as Code: How We Manage Our Company In One Monorepo At Kasava, we've embraced the concept of "everything as code" to streamline our operations and ensure consistency across our projects. This approach allows us to manage our entire company within a single monorepo, providing a unified source of truth for all our configurations, infrastructure, and applications. **Why a Monorepo?** A monorepo offers several advantages: 1. **Unified Configuration**: All our settings, from development environments to production, are stored in one place. This makes it easier to maintain consistency and reduces the risk of configuration drift. 2. **Simplified Dependency Management**: With all our code in one repository, managing dependencies becomes more straightforward. We can easily track which versions of libraries and tools are being used across different projects. 3. **Enhanced Collaboration**: A single repository fosters better collaboration among team members. Everyone has access to the same codebase, making it easier to share knowledge and work together on projects. 4. **Consistent Build and Deployment Processes**: By standardizing our build and deployment processes, we ensure that all our applications follow the same best practices. This leads to more reliable and predictable deployments. **Our Monorepo Structure** Our monorepo is organized into several key directories: - **/config**: Contains all configuration files for various environments, including development, staging, and production. - **/infrastructure**: Houses the infrastructure as code (IaC) scripts for provisioning and managing our cloud resources. - **/apps**: Includes all our applications, both internal tools and customer-facing products. - **/lib**: Stores reusable libraries and modules that can be shared across different projects. - **/scripts**: Contains utility scripts for automating various tasks, such as data migrations and backups. **Tools and Technologies** To manage our monorepo effectively, we use a combination of tools and technologies: - **Version Control**: Git is our primary version control system, and we use GitHub for hosting our repositories. - **Continuous Integration/Continuous Deployment (CI/CD)**: We employ Jenkins for automating our build, test, and deployment processes. - **Infrastructure as Code (IaC)**: Terraform is our tool of choice for managing cloud infrastructure. - **Configuration Management**: Ansible is used for configuring and managing our servers and applications. - **Monitoring and Logging**: We use Prometheus and Grafana for monitoring,
Part : This Article