DMT Tool Slowing down

Because your version or configuration or BPM's for that business object
method does not have an issue.
I have worked on lots of sites where we don't have degraded performance
so it is really something that needs to be logged with support and
escalated to investigate, if it degrades though DMT, it will overtime
for the normal client.

So the answer to the original question is it shouldn't degrade by that
much, unless other imports or activities are occurring that put strain
on the system, like backups, MRP, maintenance, Index rebuilds, etc.

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Jose Gomez
Sent: 07 February 2011 16:37
To: vantage@yahoogroups.com
Subject: Re: [Vantage] DMT Tool Slowing down...

Hi Stephen,

How come it doesn't happen when I do it on my own(by dumping the dataset
every so often)? Either-way thanks for the heads up

*Jose C Gomez*
*Software Engineer*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez>
<http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez>
<http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>

*Quis custodiet ipsos custodes?*



On Mon, Feb 7, 2011 at 11:32 AM, Stephen Edginton
<stephene@...>wrote:

>
>
> Jose,
>
> The behaviour is not related to the dataset handling, DMT refreshes
> the dataset per update.
> The issue is usually related to memory / handle leaks in the openedge
> business object server side, sometimes this can be self-inflicted from

> Data Directives / BPM's and these should be disabled to diagnose.
> It is best to load simultaneous files around 5-10 simultaneous imports

> for parts depending on server sizing and hardware to get the best
> throughput.
> Also review the version of Epicor you are using early 905.600 versions

> had issues.
>
> Regards,
> Stephen
>
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On
> Behalf Of Jose Gomez
> Sent: 07 February 2011 15:28
> To: vantage@yahoogroups.com
> Subject: Re: [Vantage] DMT Tool Slowing down...
>
> That is normal, the way the DMT works is by using the Epicor BO's
> which allow you to have multiple parts in one Data Set so the more
> parts you add the larger the dataset and the slower it will get.
> No real way around it except loading smaller files one a time like say

> 1000, stop , make a new batch etc...
>
> Its a flaw on the design of the DMT and or Epicor, we've created a
> similar tool for ourselves that in the background dumps the dataset
> every few thousand records and it works significantly better.
>
> *Jose C Gomez*
> *Software Engineer*
> *
> *T: 904.469.1524 mobile
> E: jose@...
> http://www.josecgomez.com
> <http://www.linkedin.com/in/josecgomez>
> <http://www.facebook.com/josegomez>
> <http://www.google.com/profiles/jose.gomez>
> <http://www.twitter.com/joc85>
> <http://www.josecgomez.com/professional-resume/>
> <http://www.josecgomez.com/feed/>
>
> *Quis custodiet ipsos custodes?*
>
>
> On Mon, Feb 7, 2011 at 10:14 AM, Nick <nick@...> wrote:
>
> >
> >
> > We are currently loading data into our test database. We are doing
> > part numbers and we are noticing that the DMT is slowing down as we
> > go
> along.
> > Starts out at 300 records per min and in the end, slows to about 50.
> >
> > some of our items are taking 15 hours +.
> >
> > Is this normal expected behavior or is something going on?
> >
> >
>
>
>


[Non-text portions of this message have been removed]
We are currently loading data into our test database. We are doing part
numbers and we are noticing that the DMT is slowing down as we go along.
Starts out at 300 records per min and in the end, slows to about 50.

some of our items are taking 15 hours +.

Is this normal expected behavior or is something going on?
That is normal, the way the DMT works is by using the Epicor BO's which
allow you to have multiple parts in one Data Set so the more parts you add
the larger the dataset and the slower it will get.
No real way around it except loading smaller files one a time like say 1000,
stop , make a new batch etc...

Its a flaw on the design of the DMT and or Epicor, we've created a similar
tool for ourselves that in the background dumps the dataset every few
thousand records and it works significantly better.


*Jose C Gomez*
*Software Engineer*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>

*Quis custodiet ipsos custodes?*



On Mon, Feb 7, 2011 at 10:14 AM, Nick <nick@...> wrote:

>
>
> We are currently loading data into our test database. We are doing part
> numbers and we are noticing that the DMT is slowing down as we go along.
> Starts out at 300 records per min and in the end, slows to about 50.
>
> some of our items are taking 15 hours +.
>
> Is this normal expected behavior or is something going on?
>
>


[Non-text portions of this message have been removed]
Jose,

The behaviour is not related to the dataset handling, DMT refreshes the
dataset per update.
The issue is usually related to memory / handle leaks in the openedge
business object server side, sometimes this can be self-inflicted from
Data Directives / BPM's and these should be disabled to diagnose.
It is best to load simultaneous files around 5-10 simultaneous imports
for parts depending on server sizing and hardware to get the best
throughput.
Also review the version of Epicor you are using early 905.600 versions
had issues.

Regards,
Stephen

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Jose Gomez
Sent: 07 February 2011 15:28
To: vantage@yahoogroups.com
Subject: Re: [Vantage] DMT Tool Slowing down...

That is normal, the way the DMT works is by using the Epicor BO's which
allow you to have multiple parts in one Data Set so the more parts you
add the larger the dataset and the slower it will get.
No real way around it except loading smaller files one a time like say
1000, stop , make a new batch etc...

Its a flaw on the design of the DMT and or Epicor, we've created a
similar tool for ourselves that in the background dumps the dataset
every few thousand records and it works significantly better.


*Jose C Gomez*
*Software Engineer*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez>
<http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez>
<http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>

*Quis custodiet ipsos custodes?*



On Mon, Feb 7, 2011 at 10:14 AM, Nick <nick@...> wrote:

>
>
> We are currently loading data into our test database. We are doing
> part numbers and we are noticing that the DMT is slowing down as we go
along.
> Starts out at 300 records per min and in the end, slows to about 50.
>
> some of our items are taking 15 hours +.
>
> Is this normal expected behavior or is something going on?
>
>
Hi Stephen,

How come it doesn't happen when I do it on my own(by dumping the dataset
every so often)? Either-way thanks for the heads up

*Jose C Gomez*
*Software Engineer*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>

*Quis custodiet ipsos custodes?*



On Mon, Feb 7, 2011 at 11:32 AM, Stephen Edginton
<stephene@...>wrote:

>
>
> Jose,
>
> The behaviour is not related to the dataset handling, DMT refreshes the
> dataset per update.
> The issue is usually related to memory / handle leaks in the openedge
> business object server side, sometimes this can be self-inflicted from
> Data Directives / BPM's and these should be disabled to diagnose.
> It is best to load simultaneous files around 5-10 simultaneous imports
> for parts depending on server sizing and hardware to get the best
> throughput.
> Also review the version of Epicor you are using early 905.600 versions
> had issues.
>
> Regards,
> Stephen
>
>
> -----Original Message-----
> From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
> Of Jose Gomez
> Sent: 07 February 2011 15:28
> To: vantage@yahoogroups.com
> Subject: Re: [Vantage] DMT Tool Slowing down...
>
> That is normal, the way the DMT works is by using the Epicor BO's which
> allow you to have multiple parts in one Data Set so the more parts you
> add the larger the dataset and the slower it will get.
> No real way around it except loading smaller files one a time like say
> 1000, stop , make a new batch etc...
>
> Its a flaw on the design of the DMT and or Epicor, we've created a
> similar tool for ourselves that in the background dumps the dataset
> every few thousand records and it works significantly better.
>
> *Jose C Gomez*
> *Software Engineer*
> *
> *T: 904.469.1524 mobile
> E: jose@...
> http://www.josecgomez.com
> <http://www.linkedin.com/in/josecgomez>
> <http://www.facebook.com/josegomez>
> <http://www.google.com/profiles/jose.gomez>
> <http://www.twitter.com/joc85>
> <http://www.josecgomez.com/professional-resume/>
> <http://www.josecgomez.com/feed/>
>
> *Quis custodiet ipsos custodes?*
>
>
> On Mon, Feb 7, 2011 at 10:14 AM, Nick <nick@...> wrote:
>
> >
> >
> > We are currently loading data into our test database. We are doing
> > part numbers and we are noticing that the DMT is slowing down as we go
> along.
> > Starts out at 300 records per min and in the end, slows to about 50.
> >
> > some of our items are taking 15 hours +.
> >
> > Is this normal expected behavior or is something going on?
> >
> >
>
>
>


[Non-text portions of this message have been removed]