giip
SES Proposal
GPUインフラ参照のみGPU図形AIVLMQwen3-VLローカルLLMCADRTX 5090RTX PRO 6000B200企業向けAIハードウェア構成コスト

GPU and Server Configuration for Enterprise Local Drawing AI — 20-User Reference Cost

公開日 2026-08-27 · 更新日 2026-08-27 · 最終検証日 2026-08-27

結論

Enterprise local drawing AI requires a four-part consideration: GPU selection, server configuration, AI processing pipeline, and operations. GPU tiers range from RTX 5090 (dev PoC) to RTX PRO 6000 ×2 (20-user recommended) to B200 (large-scale / 100B+ models). The AI pipeline should process drawings through VLM → Drawing JSON/Geometry IR → CAD Engine → Validator, rather than expecting a VLM to generate precise CAD coordinates directly. GPU sizing is determined by VRAM capacity, model size, concurrent requests, and response time targets — not by a simple "users ÷ GPUs" formula. B200 is unnecessary for typical 20-user enterprise workloads and should only be considered for 100B+ models, multiple concurrent VLMs, fine-tuning, or hundreds of simultaneous drawing pages.

この文書の適用条件

対象製品Enterprise Local Drawing AI Server
確認バージョンRTX 5090 / RTX PRO 6000 Blackwell / B200 / Mac M4 (as of August 2026)
適用環境On-premise (enterprise server room / colocation)
必要権限None (read-only)
実行影響None (read-only)
再起動None
最終検証日2026-08-27

そのまま実行できるコマンド

Runnable Model Sizes by GPU VRAM (as of August 2026)参照のみ
対象
NVIDIA GPUs (RTX 5090 / RTX PRO 6000 / B100 / B200)
権限
None (read-only)
変更作業
None
Production実行
N/A
# Runnable model sizes by GPU VRAM (quantization: FP16 / INT4 approximate)

VRAM 24GB (RTX 5090 single)
  FP16:   7B–13B (no quantization needed)
  INT4:   14B–30B (loadable with quantization)
  Use:    Dev PoC, personal experiments, simple drawing recognition

VRAM 48GB (RTX 6000 Ada single)
  FP16:   13B–30B (no quantization needed)
  INT4:   30B–70B (loadable with quantization)
  Use:    Extended dev PoC, simple CAD drawing recognition

VRAM 96GB (RTX PRO 6000 Blackwell single)
  FP16:   30B–50B (no quantization needed)
  INT4:   50B–110B (loadable with quantization)
  Use:    Enterprise small-scale (1–5 users), Qwen3-VL-32B single

VRAM 192GB (B200 single)
  FP16:   70B–100B (no quantization needed)
  INT4:   100B–400B+ (loadable with quantization)
  Use:    Large-scale, multiple VLM concurrent, fine-tuning

Important: Model size is not half of VRAM requirement.
Example: Qwen3-VL-32B requires ~64GB at FP16 (32B parameters × 2bytes).
Quantization (INT4) reduces this to ~16GB, but with a precision/speed tradeoff.

VRAM requirements scale with model size. Quantization reduces requirements but may degrade precision. Actual sizes vary by inference framework (llama.cpp / vLLM / Ollama).

How to Calculate GPU Count for 20 Enterprise Users参照のみ
対象
GPU sizing (enterprise environment)
権限
None (read-only)
変更作業
None
Production実行
N/A
# GPU count calculation for 20 enterprise users (example)

【Conditions】
- Model: Qwen3-VL-32B (FP16: 64GB VRAM)
- Concurrent users: 20
- Max concurrent requests: 5
- VRAM per request: ~16GB (INT4 quantized)
- Response time target: under 30 seconds
- GPU VRAM per unit: 96GB (RTX PRO 6000 Blackwell)

【Calculation】
1) Concurrent requests per GPU
   = 96GB / 16GB = 6 parallel

2) GPUs needed for 20 concurrent users
   = ceil(5 / 6) = 1 ... theoretically 1 GPU suffices

3) In practice, add margin for:
   - User growth
   - Failover capacity
   - Model update switching time
   → Recommended: 2 GPUs (replica A / replica B)

【Key point】
"20 users = 2 GPUs" is not universal.
Actual concurrent requests, drawing page count, resolution, and model size change the result.
PoC measurement is the only reliable method.

GPU count is determined by concurrent request volume and VRAM per request — not by user count alone. Measure with PoC before finalizing.

結果の読み方

意味確認するポイント
Use CaseThe use case this configuration suitsCorresponding GPU and memory configuration
GPURecommended GPU modelMemory capacity and compute performance
MemoryGPU memory or Unified Memory capacityRunnable model size and quantization conditions
Model ReferenceModel expected to run on this configurationVRAM requirements and quantization conditions
Reference Use CaseActual business application scenarioConcurrent users and throughput
Reference CostGPU unit price + full server (estimated as of August 2026)Varies by exchange rate and supply conditions

こういう状況で使います

  • Want to build local drawing AI but unsure of GPU selection criteria
  • Cannot decide between RTX 5090 and RTX PRO 6000
  • Want to know if Mac M4 or NVIDIA is better for drawing AI
  • Do not know how many GPUs are needed for 20-user drawing AI
  • Cannot determine if B200 is really necessary
  • Want to know approximate cost for enterprise drawing AI setup
  • Unclear on the role split between VLM and CAD Engine

考えられる原因(可能性の高い順)

  1. 01

    GPU selection is made "by price"

    Choosing the most powerful GPU is not the right approach. Required VRAM depends on model size, quantization rate, and concurrent requests — meaning the most effective GPU varies by these factors.

  2. 02

    The incorrect formula "users = GPU count"

    Standard GPU sizing is based on VRAM capacity and model size, not user count. Even in a 20-user environment, one GPU may suffice depending on per-request workload.

  3. 03

    VLM and CAD Engine role split is not understood

    The VLM judges "what needs to change," while the CAD Engine generates "precise coordinates and shapes." Expecting the VLM to do both leads to coordinate precision failures.

  4. 04

    B200 is being recommended beyond necessity

    B200 is the most powerful GPU, but it is overkill for typical 20-user enterprise workloads. RTX PRO 6000 × 2 is sufficient in most cases and has better cost efficiency.

確認手順

  1. 1

    Analyze current drawing workload volume and frequency

    参照のみ

    Analyze daily and monthly drawing processing volume, average pages per drawing, resolution, and format to estimate required VRAM and processing capacity.

  2. 2

    Select target model size

    参照のみ

    Reference: 4B–8B VLM for small-scale verification, 8B–32B for dev PoC, Qwen3-VL-32B or larger for production. Target model size determines required VRAM.

  3. 3

    Measure actual VRAM consumption in a PoC environment

    Send real concurrent requests with the selected model and measure VRAM usage, response time, and capacity. Measured values — not estimates — are the basis for final decisions.

対応方法

すぐに実施できる低リスクの対応

  • Measure actual user patterns in PoC

    Measure peak daily concurrent requests, drawing volume, and average processing time. Use these measured values to calculate GPU configuration. Measured data — not estimates — is the only reliable basis for sizing.

  • Separate the processing pipeline into VLM and CAD Engine

    Rather than "generating drawings with AI," structure it as "AI makes the judgment, CAD Engine generates the drawing." This simultaneously reduces VRAM requirements and improves precision.

事前検討が必要な変更

  • Expand GPU configuration in phases

    Start with RTX 5090 single GPU for PoC, then migrate to RTX PRO 6000 × 2 based on measured values. Do not purchase the final configuration upfront; expand based on PoC results.

  • Distribute requests via AI Gateway

    With a 2-GPU configuration, use AI Gateway to distribute requests across replica A and B. This improves concurrent throughput and enables degraded operations during failures.

  • Establish monitoring infrastructure

    Monitor GPU utilization, VRAM usage, response time, and throughput. Use this for early detection of capacity constraints and as the basis for scaling decisions.

専門家のレビューが必要な作業

  • Evaluate B200 adoption

    専門家レビュー必須

    Only consider B200 when ALL of the following apply: (1) 100B+ model is required, (2) multiple VLMs or agents simultaneously load the VRAM, (3) fine-tuning or large-scale training is run, (4) hundreds of drawing pages are processed across multiple projects simultaneously. RTX PRO 6000 × 2 is sufficient for typical 20-user enterprise workloads.

!注意事項

  • GPU selection is determined by VRAM capacity, model size, concurrent requests, and response time targets — not by "users ÷ GPU count."
  • "20 users = 2 GPUs" is an example, not a universal rule. Actual configuration varies based on PoC measurements.
  • B200 is unnecessary for typical 20-user enterprise workloads. Only consider it for 100B+ models, multiple concurrent loads, or fine-tuning.
  • Mac M4 Unified Memory has advantages for development and PoC, but NVIDIA is superior for production enterprise multi-user deployments due to CUDA absence.
  • GPU prices fluctuate. Reference costs are estimates as of August 2026; confirm actual prices with suppliers.
  • Expecting VLM to directly generate CAD drawings leads to coordinate precision failures. Clarify the role split.

バージョン・環境による違い

GPU model selection guide (as of August 2026)RTX 5090: dev PoC / personal experiments. RTX PRO 6000 Blackwell: enterprise single-GPU standard. RTX PRO 6000 × 2: 20-user recommended. B200: large-scale / special use cases.
Model size trendsQwen3-VL-32B requires ~64GB VRAM at FP16. Quantization (INT4) reduces this to ~16GB with a precision/speed tradeoff. Model size and VRAM requirements are proportional.
Mac M4 positioningMac M4 Max (128GB Unified Memory) is a viable option for development and PoC. MLX / llama.cpp / Ollama / Metal ecosystem is available. However, without CUDA support, NVIDIA is superior for production enterprise multi-user deployments.

これで解決しない場合に確認すること

  • Analyze actual drawing workload size distribution

    Analyze average page count, resolution, and format per drawing to derive reference values for required VRAM capacity.

  • Measure peak concurrent request volume

    Measure concurrent request peaks in the current (or similar) system to use as input for GPU configuration calculations.

  • Verify quantization precision impact

    Confirm whether output precision with INT4 quantization meets business requirements in a PoC. FP16 may be needed for precision-critical use cases.

この文書の根拠と限界

実運用で確認した内容

GPU comparison and cost estimates in this article are compiled from publicly available information as of August 2026. GPU prices and available models change; confirm actual costs with suppliers. VRAM requirements vary by inference framework.

よくある質問

Should I choose RTX 5090 or RTX PRO 6000?

RTX 5090 (32GB) for dev PoC / personal experiments; RTX PRO 6000 Blackwell (96GB) for enterprise production. RTX 5090 prioritizes development speed, RTX PRO 6000 prioritizes VRAM capacity and stability.

Is 2 GPUs really necessary? Is 1 not enough?

The reason we recommend 2 GPUs is not that 1 cannot handle 20 users. It is for: failover capacity, user growth headroom, model update switching time, and future extensibility. A PoC measurement may show 1 GPU is sufficient, in which case start with 1 and expand as needed.

Is Mac M4 suitable for drawing AI?

Viable for development and PoC. Unified Memory capacity and MLX / llama.cpp / Ollama / Metal ecosystem are advantages. However, without CUDA support, NVIDIA is superior for production enterprise multi-user deployments. A strategy of starting with Mac and migrating to NVIDIA after PoC is also valid.

Is B200 really necessary?

Unnecessary for typical 20-user enterprise workloads. B200 is only justified for: 100B+ models, multiple concurrent VLMs, fine-tuning / large-scale training, or hundreds of simultaneous drawing pages. RTX PRO 6000 × 2 is sufficient outside these conditions.

What do GPUs cost?

Estimated as of August 2026: RTX 5090 (~USD 1,500–2,500), RTX PRO 6000 Blackwell single (~USD 6,000–8,000), RTX PRO 6000 × 2 (~USD 12,000–16,000), B200 (quotation required). GPU prices fluctuate; confirm with suppliers. Full server (CPU, RAM, storage, network) is additional.

How do VLM and CAD Engine split responsibilities?

The VLM handles judgment ("what parts need what changes"), the CAD Engine handles precise coordinate and shape generation. Expecting the VLM to generate precise CAD coordinates leads to precision failures. This separation simultaneously reduces VRAM requirements and improves precision.

この文書がカバーする質問

  • What is the configuration for enterprise drawing AI server?
  • Which is better for drawing AI: RTX 5090 or RTX PRO 6000?
  • How many GPUs needed for 20-user AI server?
  • Can I build drawing AI with Mac M4?
  • Is B200 really necessary?

リスク表示の意味

  • 参照のみデータと設定を変更しません。
  • 影響は限定的ですが、権限と負荷の確認が必要です。
  • 性能・ロック・コストに影響する可能性があります。
  • 障害・データ損失・復旧作業が発生する可能性があります。
  • 専門家レビュー必須本番適用前に別途レビューが必須です。

GIIPの対応範囲

The above is general sizing guidance not tied to specific GPU products. Regarding what GIIP covers: GIIP handles the full operations layer including GPU server design and selection, model deployment and optimization, AI Gateway-based request distribution, GPU utilization and model state monitoring, incident response, model version updates, cost optimization, and capacity expansion decisions. GPU procurement and installation are the customer's responsibility, but GIIP can support the surrounding software layer and operational design.

執筆・技術検証

GIIP プロダクション運用チーム

大規模Webサービス、SQL Server、Oracle、AWS、Azureの設計・移行・運用に約30年従事。x12largeクラスのAWS RDS for SQL Server環境12セット、約12万テーブルのOracle環境、約3TBのTiDBからAurora MySQLへの移行を経験。現在も複数のクラウドデータベースと約30のWebサービスを、AIエージェントと人間の専門家が継続的に監視・運用しています。

関連サービス

GIIP can support GPU configuration validation through PoC with your actual drawings

同じ確認を複数の環境で継続する必要がある場合は、運用体制ごと相談できます。

GIIP can support GPU configuration validation through PoC with your actual drawings

ナレッジベース一覧へ