StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I would consider using <a href="http://www.microsoft.com/sqlserver/2008/en/us/compact.aspx" rel="nofollow">SQL Server Compact</a> (in-proc database from Microsoft) rather then serializing large graph of objects. </p> <p>I had experience serializing large graph to disk using BinaryFormatter. There were issues related to versioning. Serialized objects are hard to maintain and work with also. And working with such objects generally require to de-serialise into memory. It is resource consuming way to work with large graph.</p> <p>And Sql Server CE is quite lightweight, its assembly is about 1Mb. It also handles some multi-threading issues.</p> <p>If you need to serialize just to send over network or whatever, I suppose 60Mb is quite large array, there can be problems transferring it.</p> <p><strong>Update</strong></p> <p>If you would like to go with BinaryFormatter, I suppose that you can serialize your graph not as one root object but as collection of smaller objects. Perhaps it would be slower to serialize all the objects but it will let you serialize only some part of objects. If you have heterogeneous array (i.e. sequence of objects of different types) I can suppose that the more complex object is and the deeper its hierarchy the more time it takes to serialize it. You can measure serialization time for a collection of objects of the same type. You also can use some profiler to serialize the whole graph, most profilers show you which method takes more time to execute.</p>

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