StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>As @Jerry Coffin said, it really sounds like your actual problem is a memory leak. Fix that.</p> <p>But for the record, none of your "poor mans solutions" would work. At all.</p> <p>Windows pages out some of your data <em>because there's not room for it in RAM</em>. Looping through the entire memory database would load in every byte of the data model, yes... which would cause other parts of it to be paged out. In the end, you'd generate a lot of page faults, and the only difference in the end would be <em>which</em> parts of the data structure are paged out. </p> <p>Disabling the page file? Yes, if you think a hard crash is better than low performance. Windows doesn't page data out because it's fun. It does that to handle situations where it would otherwise run out of memory. If you disable the pagefile, the app will just crash when it would otherwise page out data.</p> <p>If your dataset really is so big it doesn't fit in memory, then I don't see why an SQL database would be especially "expensive". Unlike your current solution, databases are optimized for this purpose. They're meant to handle datasets too large to fit in memory, and to do this efficiently.</p> <p>It sounds like you have a memory leak. Fixing that would be the elegant, efficient and correct solution.</p> <p>If you can't do that, then either </p> <ul> <li>throw more RAM at the problem (the app ends up using 16GB? Throw 32 or 64GB at it then), or</li> <li>switch to a format that's optimized for efficient disk access (A SQL database probably)</li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload