Open GoogleCodeExporter opened 9 years ago
Here is an image comparing the memory usage.
I've also cross posted an issue with CSLA role in the memory usage. Looks like
CSLA Security consumes a lot of memory. See
http://forums.lhotka.net/forums/p/9053/43030.aspx#43030
Original comment by JenasysD...@gmail.com
on 9 Jun 2010 at 11:32
Attachments:
The memory optimisation suggested to the CSLA framework on the CSLA forum seems
to have reclaimed some of the Memory usage (100MB) which might just be enough
of a tipping point for my application and this volume of data.
Original comment by JenasysD...@gmail.com
on 9 Jun 2010 at 9:46
Nope, still get an exception during the "TransactionScope" saving of this CSLA
data with 64,000 records. Looks like the high volume of memory used by the
underlying CSLA framework is leaving limited space for the Transactions memory
requirements.
3MB Excel file become 54MB in memory via a .net Dataset then becomes 600+MB via
CSLA ER + ChildCollection containing 64,000 rows, then just blows up during the
transaction.
Original comment by JenasysD...@gmail.com
on 10 Jun 2010 at 11:35
Hello,
Did you see if passing the connections by ref made any difference?
Thanks
-Blake Niemyjski
Original comment by bniemyjski
on 10 Jun 2010 at 2:47
Tried ByRef but that fails. I'm sure it's to do with the serialization side of
things during this process.
It's also interesting the way FieldManager manager matches the number of
parameters, but doesn't match the TypeOf parameters, so you can pass items that
are not the same type (ARH). This caught me a few times.
Original comment by JenasysD...@gmail.com
on 10 Jun 2010 at 10:02
Original comment by bniemyjski
on 15 Jul 2010 at 3:48
Original comment by bniemyjski
on 9 Mar 2012 at 1:13
Original issue reported on code.google.com by
JenasysD...@gmail.com
on 9 Jun 2010 at 5:44