The CodeChef Dev team is on a mission. On a mission to make our platform stronger than ever before. In other words, when the competition gets heavy, we don’t want the platform crashing down. Now that the team has done all they could to make the platform as strong as Dwyane Johnson, we want you to come rumbling in the ring! Let’s see if the server can handle the heat when all members of the CC community come together to take part in the CodeChef Break-The-Server — An Unrated Contest With Div 3 Problems. If the server handles the footfall, well and good. If not, we get back to work. See you this Sunday, February 21, 9:30 PM.
Contest Date: February 21, Sunday
Contest Time: 9.30 PM to 10.30 PM IST
Check your timezone here
Compete Here
"Break-The-Server" ... so should I make multiple wrong submissions continuously?
I guess so, I'll be tumbling in infinite loops in my code to check its' strength!
Anyway, admirable work Codechef! :)
Hold it till after the contest.
PS: I do hope everything goes according to CodeChef's plans. :)
This aged well XD
I really liked the confidence(as strong as Dwyane Johnson) hidden behind this post!!! Lets hope it's all worth it.
CodeChef_admin should be realistic instead of believing in movies and WWE. Though i wish it will work fine.
What if they are realistic and you are underestimating?
I said "Though i wish it will work fine".
Nice mission but his name is "Dwayne Johnson" not
Dwyane Johnson.maybe they weren't talking about him but some developer team member.
Meanwhile, someone finding his DDOS.sh
Gonna be fun gain
Imagine cheating in this contest xD
Let's break the server as said by them.
Good luck CodeChef. I have doubts if this will go well. Even CF servers fail to handle load at certain times. I am not sure if CC really has a position to throw such a challenge.
Do we fail if we can't break the server?
May be a silly doubt .. but why not platforms like codeforce build using Nextjs??
Changing the entire backend architecture is a lot of work
How does it helps, kakarot__
Well Nextjs provide server-side rendering and it loads only js,css which are required thus this will load pages faster and will decrease the load on server...
Besides I also understood that this wont help a lot coz main problem is when people submit their code..and not about loading of problem statement
I'm not so sure about Codechef, but I think Codeforces renders most things on the server anyway and uses JavaScript as an utility, not as the language everything is written in. (Also this is my personal opinion, but please keep it this way forever. My user experience on Codeforces is so much better than in your typical React app.)
Will people even care to give an unrated contest ? And if not will it even be a proper test for the servers?
A bit more context:
We are testing our improved systems, and are testing rigorously. We want to ensure that the community enjoys a normal contest experience always. So we want you & your friends to participate in our Break-The-Server Contest like a normal participant, by taking part in the contest and trying to solve as many problems as you can. As in any normal contest, visit the usual pages, like the contest page, problem pages, IDE, rank list, and My Submissions pages.
This is intended to test our site infrastructure which has been the main bottleneck in the last few contests, and not the checkers. We will be improving our checkers further over the next month, but for now the focus is on the other parts of our infrastructure. So please do not try to overload the checkers with irrelevant repeated submissions — we will have a separate Break-The-Checkers testing contest for this later. For now, just participate as you normally would do in a contest. Do not post comments repeatedly.
Abide by the code of conduct.
When you realise people took your tagline too seriously. rofl
Nice "improved system"
If server breaks I will break your bones!
it did what was expected from it. problem from starting itself.
We broke the server
why its showing
Problem is not visible now. Please try again later.??Oh shit! Here we go again!
problem is not visible.
umm... I can't open the problems already T_T. Looks like someone has already broken the servers XD
Mission Successful
"Problem is not visible now. Please try again later." even after 3 minutes into the contest. LOL
UPD — Problems visible now.
We did what u told to us. We broke the server :)
I thought we were supposed to break the server, not Codechef themselves :/
Amazing improvement of servers codechef!!!
Well done Dont let anyone participate!
Upd : The servers were indeed fast. However the participation was very less compared to cook-off and lunchtime
However the participation was very less compared to cook-off and lunchtime
Obviously not everyone has time to do bullshit.
(
)
i think they forget to start the sever only , hahhha
mission failed successfully
Seems like everythings working pretty well now
yeah website is working faster without any errors while opening the problem or submitting. Good work CodeChef !
But i think number of participants are less compared to cook-off and lunchtime (people in all 3 divisions combined).
How to solve "Tree paths sum" the last problem ??May be, can be solved by using dijkstra but i have not exactly idea what to do. Only, i can use dijkstra by only source to target but can not solve target to target with that contraints :(
Can you please help by details explanation or provide the code?
read about Binary Lifting. You can solve in $$$O(logn)$$$ for each query.
If you know how to find LCA of two nodes , then you only need one dfs run to find the sum of all weights on the path from root to any node. Each query then can then be answered as W[a] + W[b] — 2*W[lca(a ,b)].
Can you please provide your code by spoiler sir :(
Code is just available in kactl library.
Read Lowest Common Ancestor on https://cp-algorithms.com/ .
I learnt this using Episode 17 — Binary Lifting, Algorithms Live!
Server was actually pretty good(except for the the first five minutes).
Thanks to everyone who participated in the contest!
The issue in the first few minutes was a very regrettable manual error from our end wrt moving the problems, and had nothing to do with the servers. Apologies for that delay.
We'll keep you updated about our future contests. Thanks once again for helping us with testing :)
Please don't disturb us again!