I have an Air application that is downloading large (~5-15GB)
files using custom chunked HTTP and writing to a FileStream. I've
noticed that when the application runs, the memory usage on the
system skyrockets. Checking the performance monitors shows that the
air application itself is not using much memory, but it is
generating a large number of page faults. The memory usage is high
(>90% on 4GB system) until shortly after the application closes
the FileStream, then it drops to like 20%.
Under the covers, how is Air doing its file I/O? It appears like all free RAM is being used to buffer the file (memory-mapped I/O?). Is there any way to control this behavior? The system really grinds to a halt while the files are downloading.
Under the covers, how is Air doing its file I/O? It appears like all free RAM is being used to buffer the file (memory-mapped I/O?). Is there any way to control this behavior? The system really grinds to a halt while the files are downloading.