0fa5b993dd
Root cause: cuMemAllocAsync (stream-ordered memory pools) produces memory that cublasLtMatmul rejects with CUBLAS_STATUS_NOT_SUPPORTED on H100 (CUDA 13.0 driver) when the matmul runs on a different stream than the allocation. Despite CUDA documentation stating same-device async allocations should be accessible from all streams with proper event synchronization, cublasLtMatmul disagrees. Proof chain: - C++ test with cudaMalloc: ALL dimensions pass on H100 ✓ - Rust test with cuMemAlloc: ALL dimensions pass on H100 ✓ - Rust test with cudarc alloc_zeros (cuMemAllocAsync): FAILS ✗ - Same dimensions, same handle, same workspace — only alloc differs Fix: set has_async_alloc=false unconditionally in CudaContext::new(). This forces cuMemAlloc_v2 for ALL allocations. Zero performance impact (allocations at construction time, not in hot loops). Also: converted has_async_alloc from bool to AtomicBool for safety. Removed diagnostic code (CUBLASLT_DIAG, test_lt_matmul_raw). Reverted cuMemAlloc workspace hack (now uses normal alloc_zeros). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Foxhunt
Production HFT trading system in Rust.
Architecture
The workspace contains 32 crates organized as follows:
Core Libraries (16)
| Crate | Purpose |
|---|---|
trading_engine |
Order processing, FIX 4.4, IB TWS, SIMD, RDTSC timing |
risk |
VaR, Kelly, circuit breakers, kill switches, compliance |
risk-data |
Risk data types and shared structures |
trading-data |
Trading data types |
ml |
DQN Rainbow, PPO, TFT, Mamba2, ensemble inference |
ml-data |
ML data types and feature definitions |
data |
Market data ingestion and storage |
backtesting |
Replay engine, strategy tester |
adaptive-strategy |
Ensemble execution, microstructure analysis |
common |
Shared types, resilience, error handling |
storage |
S3 and local model storage |
model_loader |
Model serialization and loading |
market-data |
Market data feed handlers |
database |
PostgreSQL access layer (SQLx) |
config |
Configuration management |
tli |
CLI commands and tooling |
Services (8)
| Service | Purpose |
|---|---|
backtesting_service |
gRPC backtesting service |
broker_gateway_service |
FIX routing, broker connectivity |
trading_service |
Core trading operations |
ml_training_service |
Model training orchestration |
data_acquisition_service |
Market data acquisition |
trading_agent_service |
Autonomous trading agents |
api_gateway |
gRPC API gateway with auth |
web-gateway |
Axum REST + WebSocket gateway |
Frontend
web-dashboard/ -- React 19 + TypeScript + Vite + TradingView charts.
Building
# Check compilation (no PostgreSQL required)
SQLX_OFFLINE=true cargo check --workspace
# Run tests for a specific crate
SQLX_OFFLINE=true cargo test -p <crate> --lib
# Clippy
SQLX_OFFLINE=true cargo clippy --workspace
ML Models
Four production model architectures on Candle v0.9.1 with CUDA:
- DQN Rainbow -- Deep Q-Network with prioritized replay, dueling heads, noisy nets
- PPO -- Proximal Policy Optimization with GAE and LSTM policies
- TFT -- Temporal Fusion Transformer for multi-horizon forecasting
- Mamba2 -- State space model for sequence prediction
Each model has a standalone trainer and a UnifiedTrainable adapter for the hyperopt pipeline.
Infrastructure
- Git: Gitea at
git.fxhnt.ai(Tailscale-only), Scaleway DEV1-S - Observability: OpenTelemetry OTLP (env
OTEL_EXPORTER_OTLP_ENDPOINT) - Database: PostgreSQL with SQLx offline mode for CI
License
Proprietary. All rights reserved.