Hi
Is there a relationship between the number fo table definitions in the repository and the impact on performance of the jobs?
I can think that the repository which stores everything will be impacted and that at a minimum job start-up time will be impacted, but will the runtime of a job be impacted?
I'm trying to motivate for a cleaner table definition space. I'm sure everyone will agree that the following is useless:
Category: Saved
Data Source: Aaaaa
Table Definition: _aaaaaaaaaa
Does a messy table definition repository affect performance?
Moderators: chulett, rschirm, roy
Although I concur with Craig, I can imagine a scenario when logging to the repository at 8.1 and beyond and the repository is full of both log files and table definitions that it might impact runtime performance, particularly if a lot of records get written to the job log.
<a href=http://www.worldcommunitygrid.org/team/ ... TZ9H4CGVP1 target="WCGWin">
</a>
</a>