So how long does it take for you to load up SAT10000 file?
Mine is like around 20-25mins, still got problem.

POST YOURS!!!!!

11/16/2005 2:51:55 PM

um. it shouldn't take that long. are you doing any println stuff? i remember back when i took 316 i tried testing stuff with the ole system.out.println and it took soooooo much time to do that. once i removed all the debug lines i could load the stuff in like 30 sec.

11/16/2005 3:23:10 PM

it seems like computers are faster than that

11/16/2005 3:31:57 PM

SeaCabEan,
Are you talking about loading up 167,000 lines of keys and hash them to a table, and all that takes about 30 seconds?

11/16/2005 5:18:41 PM

Unless he's changed the program/files associated with it, it shouldn't take 20-25 minutes, even on university machines. Ask him in class (like the week its due) and he'll give a good indication of what it should be.

[Edited on November 16, 2005 at 6:06 PM. Reason : .]

11/16/2005 6:06:19 PM

a poorly written algorith WILL take 30m.

you can get it to 20-60 seconds, get help from the TA.

11/16/2005 7:20:18 PM

yeah it's definitely due tomorrow so no time for any of that lol

i'm gonna be pulling an all nighter trying to finish it myself, and that probably isn't gonna happen

11/16/2005 9:29:52 PM

too impatient so we made ours to take less than 40 4 secs...dont have time for programs that take 20 to 25 minutes to run...

[Edited on November 16, 2005 at 10:54 PM. Reason : .]

11/16/2005 10:53:46 PM

mine runs an average of 3.15 seconds on SAT10000

11/16/2005 11:02:43 PM

seriously, this should run in less than 10 seconds, if i recall. If you write it in c, it's almost instantaneous.

FYI, string concatenation is slooooooow in java. If you are doing that for some reason, don't.

[Edited on November 16, 2005 at 11:13 PM. Reason : sdf]

11/16/2005 11:12:12 PM

humm.. I got my programming running on a school server in about 2mins 38 seconds... I think thats good enough for me. Hopefully not everyone in the class got it workin within seconds;

11/16/2005 11:56:59 PM

if you have ANY System.out.println("") left in there take them out... it increases the runtime by a factor of 100 litterally

11/16/2005 11:58:30 PM

we got ours down to around 6 minutes for the sat10000 one, but are next longest one (ncd4) takes like 6 seconds, so whatever.

i think he said that if you're takes 6 minutes longer than the best time or less, you're fine. so we'll be right around there.

11/17/2005 3:52:40 AM

I noticed when I run my program on my computer, it takes like 10mins, but try run it on a school machine, mine can finish in about 2 and half minutes.

11/17/2005 1:15:00 PM

so, what'd anyone else get?

for a basis of comparison, I made a little program that read all the stuff into a vector and that program takes 8 minutes on my laptop (IIRC). I don't think I ever ran the vector program on the Suns, though. I just used it to check that my program reported correct answers.
A really simple linear probing algorithm took 8 minutes on my laptop (which shouldn't be a surpise... thats what the vector essentially does), and God only knows how long that took on the Sun computers in Sullivan. I want to say it took 15 minutes on the Suns, but I'm not sure...

My program ran in about 15 seconds on my laptop and 80 seconds on the Sun's.

does the school have any free profiling software? That would have been quite helpful for me with this project...

^ there's a lot of reasons that could be happening. If your computer is older than the school machines, then that will probably happen. Or, if your computer has a lot of background processes running (read: spyware) then that will slow you down, while campus machines usually don't have that problem. You might also need to defrag, or you might not have enough memory, or whatnot. Tons of shit can cause that difference.

11/17/2005 5:44:32 PM

the vector solving program is still running on the remote eos servers, so I think we can safely assume it is asstastic, though...

11/17/2005 6:36:37 PM