Welcome to our dynamic coding contest platform, where you can practice algorithms, compete with friends, and enjoy coding challenges. Join us to enhance your coding skills and experience the excitement of real-time contests!
- Login first, then click "Create Game".
- Choose the problems for the game and set the time limit.
- Click "Create Game" to enter the game lobby, where players can join using the Game-Id.
- Click "Start Game" to observe all players' real-time code.
- Select any player to view their code for all problems and send them messages!
- When you're ready, click "Close Game" to reveal the winner!
- Click "Join Game" and enter the Game Id and your Player Name.
- Write down your solution, then click "Run" to execute example cases.
- Review the input, output, expected output, and console logs. You will also be notified if any errors are detected.
- Click "Submit" to execute all the hidden cases. If passed, see the leaderboard update!
- Once the time is up or the host closes the game, the final game results will be displayed.
| Testing Account | |
|---|---|
| [email protected] | |
| Password | test |
- Applied VM and child processes to securely execute user code and validate its output.
- Implemented a separate worker server to handle heavy tasks, preventing overload on the express server.
- Utilized a worker queue to efficiently manage traffic from the express server.
- Built the worker server with Bun instead of Node.js, resulting in a three-fold increase in user capacity.
- Implemented code error detection to notify users of any errors in their code, including excessively large output and potential infinite loops.
- Enabled real-time code updates through Redis pub-sub and Socket.IO.
- Stored game states in the database, providing players and hosts with a seamless experience by allowing them to refresh and reconnect effortlessly.
- The host can watch the progress of every player's contest and interact with them through Bullet Screen.
- Automated deployment and testing using GitHub Actions CI/CD and Docker on AWS.
After conducting load tests on APIs and Socket.IO with K6, a bottleneck was discovered in the process of executing users' code and validating the output.
The original load test for the run code API revealed the following metrics:
- Maximum virtual users: 30
- Request rate: 6 requests per second
The bottleneck appears to be occurring specifically during the execution and validation of user code.
To address the bottleneck, several important improvements have been implemented:
-
Bundling Functionality and Using an Independent Server:
- Separated code execution functionality and hosted on an independent EC2 instance, preventing server blockage and ensuring smoother performance.
-
Implementation of a Worker Queue:
- Introduced a worker queue to efficiently manage incoming requests. If the queue reaches capacity, users will be advised to run their code later.
-
Utilizing Bun JS for Faster Performance:
- Switched to Bun from Node.js to significantly improved the execution speed.
Load Test Results:
- Maximum virtual users: 100
- Request rate: 20
Selenium Test:
- Host login and start a game.
- Player joins the game and submits a solution.
- Host observes real-time updates and sends messages.
- Close the game and verify results.
selenium_test.mp4
Give credit here.