Here's the situation...
I pull customer records from a server, say 10,000. I use a proprietary framework to do so. I essentially call a query built into the framework and in a matter of time I'll have, say, a nice ArrayCollection filled with 10,000 customerDTO objects... the only problem is the memory hit of this collection is huge... 700 MB.
But if I were to instantiate and manually populate 10,000 customerDTO records locally, there is an order of magnitude difference as it's only about 70 MB.
Both methods leave me with an ArrayCollection filled with 10,000 identical CustomerDTO objects, yet when I pull it from the server there is an 1000% bump in the memory allocation.
Does anyone have any idea what may be causing this? I know the method of transport is predominantly XML - which can be quite verbose - but an order of magnitude??!?
Any thoughts would be appreciated.
I pull customer records from a server, say 10,000. I use a proprietary framework to do so. I essentially call a query built into the framework and in a matter of time I'll have, say, a nice ArrayCollection filled with 10,000 customerDTO objects... the only problem is the memory hit of this collection is huge... 700 MB.
But if I were to instantiate and manually populate 10,000 customerDTO records locally, there is an order of magnitude difference as it's only about 70 MB.
Both methods leave me with an ArrayCollection filled with 10,000 identical CustomerDTO objects, yet when I pull it from the server there is an 1000% bump in the memory allocation.
Does anyone have any idea what may be causing this? I know the method of transport is predominantly XML - which can be quite verbose - but an order of magnitude??!?
Any thoughts would be appreciated.