Question

2
Replies
666
Views
karvj Member since 2011 1 post
PEGA
Posted: 5 years ago
Last activity: 5 years 2 months ago
Closed
Solved

Large LOB Segment impacting DB Performance

In a partner-led performance test, we are seeing the PZPVSTREAM column for the table, PCA_WORK, grow to almost 10 GB after 3 hours of running the test for simulating 6,000 users.

The AWR Report for the DB is indicating a large amount of Buffer Busy Wait signals as well as direct path writes. Here is an excerpt from the AWR report showing the Buffer Busy Wait signals:

BufferBusyWait.png

The entire AWR Report is also attached (html file).

I realize that PZPVSTREAM column will likely grow to be very large in such a performance test, but 10 GB sounds like a little much. Are there any database tuning measures that should be implemented in this case?

The partner did find a document on the PDN (https://pdn.pega.com/documents/db-lob-sizing-v54) which suggested that they create a separate tablespace for the LOB segment with a larger block size and to set the chunk size equal to the average BLOB size. The document applies to version 5.4 and I was not sure if it is still applicable to Pega 7.

Does anyone have experience with LOB sizing that can chime in?

Thanks in advance.

***Updated by moderator: Lochan to close post***
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Data Integration
Moderation Team has archived post
Share this page LinkedIn