简体   繁体   English

创建了一个 session bt 它在没有更多查找缓存中花费了太多时间来通过当前并发源集中的其他并发管道构建

[英]Created one session bt it took too time in no more lookup cache to build by additional concurrent pipeline in the current concurrent source set

What will be the solution for TT_11185 no more lookup cache to build additional concurrent pipeline in the current concurrent source set becuz it taking too much time to run the session TT_11185 的解决方案是什么,不再使用查找缓存来在当前并发源集中构建额外的并发管道,因为运行 session 花费了太多时间

This normally happens when one or more lookup SQLs are taking too long to fetch the data and cache it.这通常发生在一个或多个查找 SQL 获取数据并缓存它的时间过长时。 You can do below two things -你可以做以下两件事 -

  1. Tune SQL of the lookups.调整查找的 SQL。 Check the session log carefully, identify which lookup or lookup SQL is taking time.仔细检查 session 日志,确定哪个查找或查找 SQL 需要时间。 Tune it up by adding more filters or add inner join to the source, remove unwanted columns from lookup, join on indexed columns, order by only keys, put date filter if you think its appropriate.通过添加更多过滤器或向源添加内部连接来调整它,从查找中删除不需要的列,加入索引列,仅按键排序,如果您认为合适,请放置日期过滤器。 This will help overall performance of the session and your session will take much less time.这将有助于 session 的整体性能,您的 session 将花费更少的时间。
    Now, if its a flat file lookup, then try to reduce number of rows in the file.现在,如果它是平面文件查找,则尝试减少文件中的行数。
  2. You can set session property Additional Concurrent Pipelines for Lookup Cache Creation to Auto or some numeric value like 5. This will ensure your lookups gets cached in parallel so whole session takes less time.您可以将 session 属性Additional Concurrent Pipelines for Lookup Cache Creation设置为 Auto 或某个数值(如 5)。这将确保您的查找并行缓存,因此整个 session 花费更少的时间。
  3. You can also increase DTM Buffer Size but its not necessary if there is issue with point #1.您也可以增加DTM Buffer Size ,但如果第 1 点有问题,则没有必要。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM