Moderator: Board moderators
I'm writing about Online Judge. I noticed from the server status page, http://acm.uva.es/cgi-bin/OnlineJudge?Status:Valladolid that, unless there's runtime error, all code run either under 1 second or over 10 seconds. There might be something wrong with how the judge measure the time usage.
The runtime of one of my code jumps from 10.1 seconds to 0.98 seconds just by a small optimization.
I'm pretty sure our system is OK. I've seen the stats right now, and there is a plenty of <0.1sec and >=10sec, but there are also 1.307 (1224016), 2.920 (1223965), 6.969 (1223960) and so on.
The reason for this is simple. Until some days we gave 30 secs per program. Now we only give 10 secs except particular problems. This means that all the sources that took >10sec and <30sec now get TL.
Also, our inputs and outputs are usually quite limited, so most programs either solve it quickly (remember that our system is PIII 1.5GHz [ error: it is actually 800MHz]) or they fall into infinite loops (mainly because reading the input wrongly). I really don't think that our system is broken.
BTW, we need help producing input and outputs. If you are able to, you can produce a really big input/output so programs take more time to solve and the ranking will be more accurated.
FYI, we measure the time using wait3() function. That small optimization maybe wasn't so small after all...
Ivan Golubev wrote:To fpnc
Hmm, is it real that judge system is PIII 1.5GHz? Judge status page shows ~1600 bogomips and this looks like that OJ system still running at PIII-800 processor...
Ivan Golubev wrote:Also, check out ranklist for P10399, there is a running time 1.1000 (which seems to be 2 seconds). Don't you think that it's a bit strange?
Users browsing this forum: No registered users and 1 guest