Chinaunix首页 | 论坛 | 博客
  • 博客访问: 1475123
  • 博文数量: 931
  • 博客积分: 10
  • 博客等级: 民兵
  • 技术积分: 10198
  • 用 户 组: 普通用户
  • 注册时间: 2011-07-08 12:28
个人简介

测试

文章分类

全部博文(931)

文章存档

2020年(134)

2019年(792)

2018年(5)

我的朋友

分类: 架构设计与优化

2020-02-08 12:06:31

In My appointment application, when jerry clicks F4 on account field, there will be odata request to retrieve account information.

To my surprise, this odata request took more than one minute to get response:

Then I did a performance trace in jerry system and found out most time is spent on your code CL_CRM_BP_ODATA_RT~ SELECT_ENTITYSET_BY_SQL.

I wrote a report in jerry system MOR/300 to reproduce this performance issue, report name: ZTEST_APP_PERFORMANCE. Simply execute it and you will find the issue.

In jerry system there are 645,212 entries in BUT000, and in AG3/001 I execute the same report ( report name: ZSEARCH_BP_IN_APPOINTMENT ) with BUT000 entries 60,452.

The performance of these two systems are quite different, even considering the table volume difference:

In jerry system: 645,212 entries, 81 seconds

In AG3/001: 60,452 entries, 0.178 second

Even if I disable the authorization related search field,

The performance is a little bit improved but still bad: 645,212 entries, 56 seconds

I am using MaxDB.

阅读(962) | 评论(0) | 转发(0) |
给主人留下些什么吧!~~