I was doing a little blog hopping, and I happen to read this particular entry in one blog. It's regarding CORS and the recent long downtime during round 1A. It says:
Citing reasons attributing from the Taiwan earthquake to the overloading of servers, this reflects the lack of backup servers for the CORS system during every semester's bidding exercise.
Backup servers? Har?
I don't think CORS is that simple. It's far more complex. And what has a local server got to do with something happening in Taiwan? It's like saying that you are in Jurong East now, and you want to go to Clementi, and you took the North-South line to Raffles Place and then taking the East-West line to Clementi.
Overloading is quite inevitable during the bidding period, unless you are going to limit the time when people from a certain level entering the system, which will just defeats the purpose for having a bidding system. And CORS is not Google or Yahoo. It's not that the system will get millions of hits per second to call for redundant servers.
Cost effectiveness.
1 thing that I don't really like about the system is that I have to add in a module into my list before I can see its bidding statistics during a particular round. I would really like to be able to see the bidding information right at the point before I add in the module for bidding. I have actually reflected that into the previous survey on CORS, but it looks like it will not be implemented anyway.
If nothing goes wrong, I will be out of NUS by 2008. Change or not, it doesn't matter too much to me. Not that I don't care, it's just that care is not being taken into account.
Oh well. Don't care. As long as bidding still works, so be it. Lol.
Anyway, bidding is over. 6 modules. All over NUS. So fun!