With most disk accessing methods, there are considerable overheads involved, including disk seek and access times. By implementing a file in memory, many performance gains can be achieved.
Yesterdays presentations went rather well, I thought the class did a good job and put in a fair amount of effort. I really look forward to their final projects, hopefully they all finish.
I've started to develop my own engine, after being disenchanted by various new engines I've seen, plus I have a few ideas that would be really neat.
Some things I hope to feature:
Hrm my server went down for some strange reason... ahh well, seems to be fixed (for now). I think I need to implement some sort of redundancy or recovery measures.
Well today I start the second class, it seems to have went better than the first time, well most of that is because of how bad that was. Its true, you always learn from mistakes. In fact I kinda feel sorry for the first class now. I do not think the first class are ready for photo reconstruction yet, they can barely manage selecting something :(
Man monday was a bad day for me, more than usual. I felt sick, missed uni, and was late for work. Wow that sucked.
I hate uni, I cant wait until its over.
No its not a new children's TV show, I'm just deciding to stick with the slowness as it is only when altering content, anonymous views are cached and from what I hear not as bad.
Also I may be setting up drupal for a university website for the games diploma, as I mentioned to them it would be a much for effective promotional tool to have an online presence rather than a newspaper ad, since most of the new recruits for that course don't seem to read the paper anyway.