Skip to Content
0

Design Studio Reports Memory Consumption Increases After Refresh

Jan 26, 2017 at 11:31 AM

91

avatar image

Hi,

I have an dashboard with two pages, I display pages 30 seconds intervals (using timer component). Every refresh I realized that memory consumption is increasing 4-5 mb and after 3-4 hours Internet Explorer is freezing.

I realized that info charts causing the problem, I change info charts to chart, memory consumption is less than info charts but problem still exists.

Have you ever encounter such problem?

Regards.

10 |10000 characters needed characters left characters exceeded

Hello - what is your data source? If it is BW, I would expect caching to help - see https://blogs.sap.com/2016/07/26/use-of-bw-cache-in-sap-design-studio/ and https://blogs.sap.com/2015/05/22/design-studio-performance-best-practices/

Also what version of Design Studio are you using? Are you using profiling?

0

Hi,

Data source: Sybase IQ 16

Design Studio 1.6

The main problem is a memory leak not the performance, whenever I change visibility of chart , memory usage is increasing.

You can simulate problem by creating a report with charts and changing their visibilty. You can see that memory consumption is growing in every change.

Regards.

0
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Tammy Powlas
Jan 26, 2017 at 12:54 PM
0

Reading previous posts - see https://archive.sap.com/discussions/thread/3739886 with Mike's comment here "I'd caution against polling on an interval as you eventually will trigger a JVM memory leak with too many callRuntimeHandler calls over and over."

He also has a suggestion here https://blogs.sap.com/2015/05/20/whats-new-in-design-studio-15-sdk/#comment-590185 (see 2nd comment)

Share
10 |10000 characters needed characters left characters exceeded
Hasan HATIRNAZ Jan 26, 2017 at 01:55 PM
0

Hi,

I can not understand how I can prevent this memory leak,

Regards.

Show 1 Share
10 |10000 characters needed characters left characters exceeded

From the links above, Mike says this: "I'd caution against polling on an interval as you eventually will trigger a JVM memory leak with too many callRuntimeHandler calls over and over."

0