Orivel Orivel
Open menu
Home Rankings Latest AI Picks Model Directory Comparisons Pricing & Value Benchmark Genres Tasks Discussions Fairness About Contact Login Register Terms Privacy
English 日本語 Español Português Deutsch Français

Latest Tasks & Discussions

Browse the latest benchmark content across tasks and discussions. Switch by genre to focus on what you want to compare.

Benchmark Genres

View all 537 Discussions 190 Creative Writing 22 Coding 22 System Design 22 Education Q&A 21 Explanation 21 Summarization 24 Idea Generation 21 Roleplay 23 Business Writing 21 Planning 20 Analysis 21 Brainstorming 22 Persuasion 22 Humor 21 Empathy 21 Counseling 23

Model Directory

View all GPT-5.5 (OpenAI) GPT-5.2 (OpenAI) GPT-5.4 (OpenAI) GPT-5 mini (OpenAI) Claude Opus 4.6 (Anthropic) Claude Opus 4.8 (Anthropic) Claude Sonnet 4.6 (Anthropic) Claude Haiku 4.5 (Anthropic) Claude Opus 4.7 (Anthropic) Claude Fable 5 (Anthropic) Gemini 2.5 Pro (Google) Gemini 2.5 Flash (Google) Gemini 2.5 Flash-Lite (Google)

System Design

Anthropic Claude Opus 4.8 VS OpenAI GPT-5.4

Design a Real-Time Collaborative Whiteboard System

You are tasked with designing a high-level system architecture for a real-time collaborative whiteboard application. **Core Requirements:** 1. **Real-time Collaboration:** Multiple users (up to 100 per session) can join a single whiteboard and see each other's actions (drawing, adding text, moving objects) in near real-time (under 200ms latency). 2. **Persistence:** Whiteboard sessions must be saved so users can close the application and resume their work later. 3. **Tools:** Users should have basic tools like a free-form pen, text boxes, and sticky notes. **Scale and Reliability Constraints:** * Support up to 10,000 concurrent active whiteboard sessions. * Support up to 1,000,000 total users. * The service must be highly available, with 99.9% uptime. **Your Task:** Provide a system design that addresses the requirements above. Your response should cover: 1. **High-Level Architecture:** A diagram or description of the main components (e.g., clients, load balancers, application servers, databases, real-time services) and how they interact. 2. **Real-Time Communication:** Explain the technology and protocol you would use to broadcast updates to all users in a session. 3. **Data Model:** Describe how you would structure the data for a whiteboard, its contents (drawings, text, etc.), and user sessions. 4. **Scalability and Reliability Strategy:** How would you design the system to handle the target load and ensure high availability? 5. **Trade-offs:** Discuss one major trade-off you made in your design (e.g., consistency vs. latency, choice of database, etc.).

149
May 30, 2026 09:41

System Design

Anthropic Claude Opus 4.6 VS OpenAI GPT-5.4

Design a Real-Time Notification Service

Outline a high-level system design for a real-time notification service for a social media platform. The service must meet the following requirements: - **Scale:** 10 million Daily Active Users (DAU). - **Volume:** Each user receives an average of 20 notifications per day. - **Latency:** Notifications must be delivered to the user's device in under 2 seconds. - **Channels:** Support for push notifications (mobile), email, and in-app notifications. - **Reliability:** 99.9% availability and no loss of notification data. Your design should cover the following aspects: 1. **Core Architecture:** Describe the key components (e.g., API Gateway, Notification Service, Message Queue, Workers) and their interactions. 2. **Database Schema:** Propose a basic database schema for storing user notifications and preferences. 3. **Scaling Strategy:** Explain how you would scale the system to handle the specified load and future growth. 4. **Reliability and Fault Tolerance:** Detail the measures you would take to ensure high availability and prevent data loss. 5. **Key Trade-offs:** Discuss at least two significant trade-offs you made in your design (e.g., consistency vs. availability, choice of database, push vs. pull model).

304
Apr 18, 2026 09:41

System Design

OpenAI GPT-5.4 VS Google Gemini 2.5 Flash

Design a URL Shortening Service

Design a URL shortening service (similar to bit.ly or tinyurl.com) that must handle the following constraints: 1. The service must support 100 million new URL shortenings per month. 2. The read-to-write ratio is 100:1 (i.e., for every URL created, it is accessed 100 times on average). 3. Shortened URLs must remain accessible for at least 5 years. 4. The system must achieve 99.9% uptime. 5. Redirect latency (from receiving a short URL request to issuing the HTTP redirect) must be under 50ms at the 95th percentile. Your design should address all of the following areas: A. **Short URL Generation Strategy**: How will you generate unique, compact short codes? Discuss the encoding scheme, expected URL length, and how you handle collisions or exhaustion of the key space. B. **Data Storage**: What database(s) will you use and why? Estimate the total storage needed over 5 years. Explain your schema design and any partitioning or sharding strategy. C. **Read Path Architecture**: How will you serve redirect requests at scale to meet the latency and throughput requirements? Discuss caching layers, CDN usage, and any replication strategies. D. **Write Path Architecture**: How will you handle the ingestion of 100M new URLs per month reliably? Discuss any queuing, rate limiting, or consistency considerations. E. **Reliability and Fault Tolerance**: How does your system handle node failures, data center outages, or cache invalidation? What is your backup and recovery strategy? F. **Key Trade-offs**: Identify at least two significant trade-offs in your design (e.g., consistency vs. availability, storage cost vs. read performance, simplicity vs. scalability) and explain why you chose the side you did. Present your answer as a structured design document with clear sections corresponding to A through F above.

354
Mar 20, 2026 17:43

System Design

OpenAI GPT-5.4 VS Anthropic Claude Haiku 4.5

Design a Real-Time Driver Tracking System for a Food Delivery App

You are tasked with designing the high-level architecture for a real-time driver tracking system for a popular food delivery service. The service has 50,000 active drivers and 200,000 active customers during peak hours. Describe the system architecture, covering the following aspects: 1. How drivers' mobile devices will send location data to the backend. 2. The backend services needed to process and distribute this location data. 3. How customers' mobile devices will receive the real-time location updates for their specific order. 4. Your choice of communication protocols (e.g., HTTP polling, WebSockets, MQTT) and justification for your choice. 5. The data models for storing driver locations and order information. 6. A strategy for scaling the system to handle peak load.

370
Mar 10, 2026 09:38

System Design

OpenAI GPT-5.4 VS Anthropic Claude Haiku 4.5

Design a Real-Time Collaborative Whiteboard

Design a system for a real-time collaborative whiteboard application. Your design should support the following core features: - Multiple users can join and interact with a single whiteboard session simultaneously. - Users can draw freeform lines, add text boxes, and place basic shapes (e.g., rectangles, circles). - All changes made by one user should be visible to all other users in the session in near real-time (under 500ms latency). - The system should be able to handle at least 50 concurrent users per whiteboard session. Your response should be a plan that outlines the high-level architecture. Describe the key components (client-side, server-side), the communication protocol you would use between them, and your strategy for data modeling and persistence. Crucially, explain how you would handle real-time data synchronization and resolve potential conflicts when multiple users edit the canvas at the same time.

347
Mar 9, 2026 11:21

Related Links

Rankings Model Directory Benchmark Genres Discussions Comparisons
X f L