SMAT DB Optimal Settings for SmatHistory Options

[Mike Itani]

Hello,

We recently turned on SMAT DB and things are going great until we realize how quick those file grew and we had sizing issues, where the SmatHistory Total size  was rapidly reaching the max amount.

Reaching out to the community to see how did you configure your settings and whether there was an issues with relatively higher sized files.

Here is how the current setup is

Process -> Configure
Automatic SMAT Cycling Threshold: 100 MB
—————————————–

Smat History options:

SMAT Total Files: 100
SMAT Total Size: 1,000 MB
Smat Max Age: 30 Days

 

Thank you for your assistance.

Topic

[Matthew Brophy]

we encountered search performance issues when files were quite large (+1 GB)

I may be looking at this wrong, but I have noticed that when defining the site SMAT criteria, it looks like it takes the larger of the three values. (i.e. size limit = 100 MB age limit = 14 days….. SMAT will exceed 100 MB to store 14 days worth).

I understand the best practice sizing is SMAT size 100GB / 1 million transactions.

So if you only wanted to keep 50,000 messages, you would size 5GB

Sizing of a Cloverleaf site would be for 1/2 the disk to recovery DB and the other 1/2 for SMAT archiving.

[Mike Itani]

Thanks Mattew for your feedback. We are trying to stick with 100MB smat db sizes to avoid the performance issues.

As for SMAT Criteria for us we hit the max size of 1GB and it started purging.

 

Are you guys doing any compressing of SMAT?

[Author]

Replies