disk monitoring - Page 108

1TB data on disk with around 1KB per data record. How to find duplicates using 512MB RAM and infinit

- by user288609

1TB data on disk with around 1KB per data record. How to find duplicates using 512MB RAM and infinite disk space?

Combining FileStream and MemoryStream to avoid disk accesses/paging while receiving gigabytes of data?

- by w128

I'm receiving a file as a stream of byte[] data packets (total size isn't known in advance) that I need to store somewhere before processing it immediately after it's been received (I can't do the processing on the fly). Total received file size can vary from as small as 10 KB to over 4 GB. One option for storing the received data is to use a MemoryStream, i.e. a sequence of MemoryStream.Write(bufferReceived, 0, count) calls to store the received packets. This is very simple, but obviously will result in out of memory exception for large files. An alternative option is to use a FileStream, i.e. FileStream.Write(bufferReceived, 0, count). This way, no out of memory exceptions will occur, but what I'm unsure about is bad performance due to disk writes (which I don't want to occur as long as plenty of memory is still available) - I'd like to avoid disk access as much as possible, but I don't know of a way to control this. I did some testing and most of the time, there seems to be little performance difference between say 10 000 consecutive calls of MemoryStream.Write() vs FileStream.Write(), but a lot seems to depend on buffer size and the total amount of data in question (i.e the number of writes). Obviously, MemoryStream size reallocation is also a factor. Does it make sense to use a combination of MemoryStream and FileStream, i.e. write to memory stream by default, but once the total amount of data received is over e.g. 500 MB, write it to FileStream; then, read in chunks from both streams for processing the received data (first process 500 MB from the MemoryStream, dispose it, then read from FileStream)? Another solution is to use a custom memory stream implementation that doesn't require continuous address space for internal array allocation (i.e. a linked list of memory streams); this way, at least on 64-bit environments, out of memory exceptions should no longer be an issue. Con: extra work, more room for mistakes. So how do FileStream vs MemoryStream read/writes behave in terms of disk access and memory caching, i.e. data size/performance balance. I would expect that as long as enough RAM is available, FileStream would internally read/write from memory (cache) anyway, and virtual memory would take care of the rest. But I don't know how often FileStream will explicitly access a disk when being written to. Any help would be appreciated.

Search Results

Search found 11115 results on 445 pages for 'disk monitoring'.

Page 108/445 | < Previous Page | 104 105 106 107 108 109 110 111 112 113 114 115 | Next Page >

- by user288609

- by w128

- by user288609

- by serialhobbyist

- by pedromarce

- by arcyqwerty

- by Abu

- by miernik

- by Jason Fitzpatrick

- by Pedram

- by con-f-use

- by searchfgold6789

- by TardisGuy

- by cheshirekow

- by blesh

- by Larry Harson

- by JK04

- by boywithaxe

- by Dennis Schma

- by blesh

- by surlogics

- by TardisGuy

< Previous Page | 104 105 106 107 108 109 110 111 112 113 114 115 | Next Page >