Webmonkey26
2010-02-09 14:01:01 UTC
We have written a simple app that executes a simple DTS package constantly to
monitor memory. We were expecting to see memory usage maintained at the same
level as the package is not actually doing anything with the data, however we
are seeing a small, steady increase in memory consumed by the executing
process.
.NET code that calls the execution looks like...
XmlDocument packageXml = new XmlDocument();
packageXml.Load("c:\\test.dtsx");
Package package = new Package();
package.LoadFromXML(packageXml, null);
while (1 > 0)
{
package.Execute();
}
We run this in a console app and memory seems to creap up at the rate of
approx 12kb's per second.
If we re-run the test with the package.Execute(); commented out then memory
usage remains fixed and does not increase.
The DTSX package is as simple as they come, its just a single dataflow task
that reads from a small table with < 20 rows and does nothing with the data.
Anyone seen anything like this before? or any clues what might be causing
the leak?
Thanks
WebMonkey
monitor memory. We were expecting to see memory usage maintained at the same
level as the package is not actually doing anything with the data, however we
are seeing a small, steady increase in memory consumed by the executing
process.
.NET code that calls the execution looks like...
XmlDocument packageXml = new XmlDocument();
packageXml.Load("c:\\test.dtsx");
Package package = new Package();
package.LoadFromXML(packageXml, null);
while (1 > 0)
{
package.Execute();
}
We run this in a console app and memory seems to creap up at the rate of
approx 12kb's per second.
If we re-run the test with the package.Execute(); commented out then memory
usage remains fixed and does not increase.
The DTSX package is as simple as they come, its just a single dataflow task
that reads from a small table with < 20 rows and does nothing with the data.
Anyone seen anything like this before? or any clues what might be causing
the leak?
Thanks
WebMonkey