Ulrich G. Kliegis
Yes, Ulrich, I can see the events on your graphs. Be careful withYes. I thought about moving the virtual memory to the RAM disk, but then,
after some deep thinking... :)
Nope, not really.
I have a SSD on one of my new systems in the office, but that's reserved for
Using two physical disks is a much better solution - perhaps systemSee, I have three HDDs: C: has system and your software, D: only things
like setup-files, E: all MSG stuff (including the MSG-related receiving- and
received folders, F. the same for NOAA-AVHRR and Metop.
FSY of course on the RAM disk.
I would recommend having a real-time defragmenter running - with theToo many software fragments... :)
And since Windows 7, it's a fashionable must to have some 7 in the brand.
I follow the not more than a few steps at once strategy now, installed an
older mst defrag that I still had here (3.6) and started it. Well, it's doing its
work, and you all can see of it will decrease the missed packets count. The
degree of fragmentation on E: and F: was considerable...
Both will defrag "when needed" by monitoring the disk state.mst reagards idle times - although these do not really happen, but it seems
to stay rather politely in the background.
From the TelliCast configuration standpoint:Well, I suppose they are the reason for the FSY files growing (after the
reboot last night) - there is no other explanation.
My rationale was: If I dispatch the data already in the beginning to the
correct partition, they don't have to be pushed around again. And the disk
heads have it a bit easier, maybe.
Like in my case, see above.