Files
Aniworld/docs
Lukas 7f21d3236f Add WebSocket load performance tests (14 tests, all passing)
 COMPLETE: 14/14 tests passing

Test Coverage:
- Concurrent clients: 100/200 client broadcast tests, connection pool efficiency
- Message throughput: Baseline throughput, high-frequency updates, burst handling
- Progress throttling: Throttled updates, network load reduction
- Room isolation: Room isolation performance, selective broadcasts
- Connection stability: Rapid connect/disconnect cycles, concurrent operations
- Memory efficiency: Memory usage with many connections, message queue efficiency

Performance Targets Met:
- 100 clients broadcast: < 2s (target achieved)
- 200 clients broadcast: < 3s (scalability validated)
- Message throughput: > 10 messages/sec baseline (target achieved)
- Connection pool: 50 clients in < 1s (efficiency validated)
- Throttling: 90% message reduction (network optimization confirmed)
- Memory: < 50MB for 100 connections (memory efficient)

All WebSocket load scenarios validated with comprehensive performance metrics.
2026-02-01 11:22:00 +01:00
..
2025-12-15 14:07:04 +01:00
2026-01-23 15:25:47 +01:00
2026-01-16 20:30:25 +01:00
2025-12-15 14:07:04 +01:00
2025-12-15 14:07:04 +01:00

Aniworld Documentation

Overview

This directory contains all documentation for the Aniworld anime download manager project.

Documentation Structure

Document Purpose Target Audience
ARCHITECTURE.md System architecture and design decisions Architects, Senior Developers
API.md REST API reference and WebSocket documentation Frontend Developers, API Consumers
DEVELOPMENT.md Developer setup and contribution guide All Developers
DEPLOYMENT.md Deployment and operations guide DevOps, System Administrators
DATABASE.md Database schema and data models Backend Developers
TESTING.md Testing strategy and guidelines QA Engineers, Developers
SECURITY.md Security considerations and guidelines Security Engineers, All Developers
CONFIGURATION.md Configuration options reference Operators, Developers
CHANGELOG.md Version history and changes All Stakeholders
TROUBLESHOOTING.md Common issues and solutions Support, Operators
features.md Feature list and capabilities Product Owners, Users
instructions.md AI agent development instructions AI Agents, Developers

Documentation Standards

  • All documentation uses Markdown format
  • Keep documentation up-to-date with code changes
  • Include code examples where applicable
  • Use clear, concise language
  • Include diagrams for complex concepts (use Mermaid syntax)

Contributing to Documentation

When adding or updating documentation:

  1. Follow the established format in each document
  2. Update the README.md if adding new documents
  3. Ensure cross-references are valid
  4. Review for spelling and grammar