Menu
  • HOME
  • TAGS

Issues parsing a 1GB json file using JSON.NET

json,parsing,stream,json.net,large-object-heap

Thanks for all the help, I've managed to get it doing what I want which is de-serializing individual location objects. If the item is converted to a JObject it will read in the full object and de-serialize it, this can be looped to get the solution. This is the code...

Extensive use of LOH causes significant performance issue

c#,performance,garbage-collection,large-object-heap

The performance problems usually come from two areas: allocation and fragmentation. Allocation The runtime guarantees clean memory so spends cycles cleaning it. When you allocate a large object, that's a lot of memory and starts to add milliseconds to a single allocation (when lets be honest, simple allocation in .NET...

Get list of object instances that are in LOH

.net,windbg,sos,large-object-heap,sosex

To get all objects on LOH you can use SOS !dumpheap with the -min option. !dumpheap -min 85001 To limit the output to the type of objects you're looking for, first determine the method table (MT) of your object by doing a !dumpheap -type <MyClass> Address MT Size 03653250 785037b8...

Objects added to the Large Object Heap

c#,large-object-heap

You are right that if array is larger than 85000 then it will be consider as LOH not entire object. To explain this here I created example. class Program { static void Main(string[] args) { Obj o = new Obj(); o.Allocate(85000); Console.WriteLine(System.GC.GetGeneration(o)); Console.WriteLine(System.GC.GetGeneration(o.items)); Console.WriteLine(System.GC.GetGeneration(o.items2)); Console.WriteLine(System.GC.GetGeneration(o.Data)); Console.ReadLine(); } class Obj {...