Bandwidth Usage on the Event of Result Publishing (May 06, 2018 at 1:00 PM):

Result Served:

[SSC-2018] Result Served total, on 06 May 2018:
At 13:00-13:59: 1122032
At 14:00-14:59: 1362500
At 15:00-15:59: 741106
At 16:00-16:59: 396379
At 17:00-17:59: 300275
All day (13:00-23:59): 4842120

[SSC-2018] PDF Result Download total, on 06 May 2018:
At 13:00-13:59: 77229
At 14:00-14:59: 59805
At 15:00-15:59: 35590
At 16:00-16:59: 20655
At 17:00-17:59: 13400
All day (13:00-23:59): 248761

About the CAPTCHA (Security Key) used:
Example: captcha

CAPTCHA Engine is completely written in ANSI C in Linux Environment. It is very lightweight and it has its own Event-based HTTP Server (Hand Coded C from Scratch) which can handle around 500000 (Five Lac) requests per Second (Static Response, tested from Same Local Machine). This helped us handle the load properly this time. To save bandwidth for real result service we had to disable serving captcha (only for Details Result) for some time. Captcha Engine itself can serve over 150000 (One Lac Fifty Thousand) Random Captcha per Second from pre-generated Images (used dictionary of words). Due to Limitation of PHP to send request to Captcha Engine to Fetch Captcha our Benchmark showed that we could serve over 17000 (Seventeen thousand) Captcha per Second (tested from Same Local Machine as of the Service).
We are always working on making best use of Hardware and Software Technologies to serve people better.

Server 1: Serves Static CSS/Javascript, CAPTCHA (Security Key), Result of various types, Result Analytics and all dynamic Information
server-1.png

Server 2: Serves Static CSS/Javascript, Subject Code, Stores Statistical data
server-2.png