Some strange observations

[Screet]

Hi,

I did notice that Oolite has a constant addition of roughly 1100 IO read bytes per update interval in the task manager. Is this normal? What is Oolite reading all the time? Can this slow down the game?

Solas did suggest that I try the ProcessMonitor on Oolite. Turns out that there is a constant flow of 50-500 transactions per update interval there.

Process Monitor does only show the first few transactions to me (70K) of the 870K transactions that have been reached in the first 5 minutes or so.

Strangely, almost all transactions are reported as reads on PowerSchemes and PowerSettings of the registry?!?

Is this normal? I bet that this could slow the game down immensely.

Screet

[Kaks]

Intriguing, the only possible reason why Oolite would need to read power settings is to stop screensavers (& HD shuttting off maybe?) when in full screen.

I haven't come across any code that checks the registry, but the most likely source of that should be the SDL library, it does do the bulk of the cross platform stuff...

On the plus side, most of the registry is never paged, and if a particular location is queried time and again it's left on the cache: doing a memory read can take up very, very little time... 2 or 3 clock cycles per read in most cases.

1000 memory reads would thus take 3000 clock cycles, which translates to 0.000003 of a second in a 1Ghz single core processor, if I got my math right! Still, every little helps!