So, like I said, I did a few 32M runs yesterday, made an excel sheet in which I put the time of every loop and the time difference between a loop and the preceding loop. I can share my excel-file if someone wants it ... not that special, though.
During the testing I've switched to a faster sata drive with more cache. I gained a bit more than 1 second.
This is the pic with the two segments I talked about. The first area will be explained later, the second one is quite important. It shows the difference in time between the loop24/output and loop23/loop24 ("/" is not the symbol of division). Normally, loop24/output should be about 1 second faster than loop23/loop24, in my case I can't do this. My times would be 2 seconds faster.
The first segment I talked about is very interesting. It shows an almost lineair decrease.
Line3: ran superpi from C, while pagefile on D. Used 3x632 files and copied from D to C first. IDE hdd for page
Line2: ran superpi from D; while pagefile on D. Used 3x632 and copied from D to C first. IDE hdd for page
Line1: ran superpi from D, while pagefile on D. Used 1 file exactly 3x632MB and copied from C to D first. Sata HDD for page.
I need to do some extra testing before I can jump to conclusions. But there are a few things that catched my eye.
- The faster you get that lineair decrease, the better the time.
- Running superpi from the same harddisk as the pagefile is on will be slower if not properly tweaked, but if well-tweaked = faster.
- Pi from page HDD = slower loop24/output.
- The size of the systemcache is important (the higher, the better), BUT available memory must be the same size of the systemcache to get the best results!
NOTE: Initial time was 14m32s, after some testing I went to 13m59s, now I'm at 13m56s.
Reply With Quote
Bookmarks