{"image_url":null,"blog_url":"https://yohei-a.hatenablog.jp/","provider_name":"Hatena Blog","categories":["Teradata"],"height":"190","width":"100%","blog_title":"ablog","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fyohei-a.hatenablog.jp%2Fentry%2F20211108%2F1636323862\" title=\"Teradata \u306e AWT \u3068\u306f - ablog\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","type":"rich","published":"2021-11-08 07:24:22","author_name":"yohei-a","provider_url":"https://hatena.blog","version":"1.0","description":"AWTs are the smallest unit of work in Teradata. These are the tasks or execution threads inside of each AMP that get the database work done, such as executing a query step once the step is dispatched to the AMP. Each AMP has up to 80 AMP worker tasks available to them. AWTs can be increased from 80 \u2026","url":"https://yohei-a.hatenablog.jp/entry/20211108/1636323862","author_url":"https://blog.hatena.ne.jp/yohei-a/","title":"Teradata \u306e AWT \u3068\u306f"}