This is a thread, one of a series over the years, dedicated to general stats about the Chief Delphi thread about the speed, strength and direction of team & event registration for FRC. As we’ve seen already, it’s going to be an exciting year in Mark McLeod’s Registration 2017 thread here on Chief Delphi!
Is the initial registration experience “typically” bad?
As we’ve seen today, the retooled Dashboard/TIMS system could just not hold up to the load of initial event registration. Is this a “typical” experience? Should we be accustomed to this?
Let’s take a brief look at what has occurred in previous years. Below are some quotes that tell parts of the tale. In two of the past years we looked at, the “Registration YYYY” thread here on Chief Delphi indicated a problem with the initial registration process. From these posts, we can surmise that in 2012, TIMS was very slow during initial event registration. Two years before, in 2010, TIMS was brought completely down by the load of hundreds of teams attempting to register simultaneously for the first time that season. In the 10-year period (inclusive of 2008-2017) of “Registration YYYY” threads under study, we see that there were 3 years when TIMS was reported as laggy, unusable, or down for a majority of people attempting to do initial registration.
Is this the part where I complain about the CD overload yesterday that prevented me from viewing or editing posts on the Registration thread at the height of the server crash?
It would be pretty useful if you made a thread to analyse the CD load yesterday preventing people from loading your Registration thread during the server crash.
Mark should start another 2017 registration thread that doesn’t have 12 pages of server crash discussions (are whatever). Or maybe a moderator could branch that off the original thread.