Approximate time to expiration of reports

Previous topic - Next topic

jose.arotinco

Hi,

Can you give me an approximate time of how long take to expire reports from cache the a server with the following characteristics:

Applications Group: 1350 approx
Cache Document Data for: 90 Days
Years of information: 02 years

it is the first time I'll run the command arsmaint -crsv and not know how long it will take.

And also some additional recommendations .

Thank you.
Regards,

Justin Derrick

There are really too many factors to be able to reliably tell you how long it will take.  You didn't mention platform, CPUs, RAM, I/O bandwidth, Expiration Type, or how many records are in each Application Group.  Even with ALL that information, it would still be nearly impossible to give an accurate estimate.

If you're concerned about the expiration running over a long period and affecting customers, you can either start at a period of low activity (long weekend?  summer holidays?) or use the -g option in arsmaint to only process specific Application Groups.

Good luck!

-JD.
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Webinars:  https://CMOD.Training/
IBM CMOD Professional Services: https://CMOD.cloud

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

jeffs42885

Just an FYI-

Last time I was involved in something like this we engaged the folks at IBM professional services, and granted it wasnt 5x40 work, it took a long time.

What kind of data is it?

jose.arotinco

Justin,
Thanks for the reply, the features are:

Platform: Windows Server EE
RAM: 8GB
Expiration Type: Load
Record in each AG: approx 3500, there are about 10 AG with over 100,000 records

I had thought the expiration run everyday, but I see it will not be a good idea.

jeffs42885,
The loaded data are text files...sorry but I do not understand when you say 5x40, that you mean that ...?

did not know that the subject of serious expiration complicated, some other additional thing that can recommend me? With all the features mentioned can be given approximately how many hours can take?

Thanks



Justin Derrick

Hi Jose.  :)

Like I said, even with ALL the information, it would still be just a guess.  Run one expiration, see how long it takes, count how many documents you started with, and how many were expired to get an idea of how well that performs, then do some other Application Groups.  The only way to get real numbers is to do some testing.

-JD.
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Webinars:  https://CMOD.Training/
IBM CMOD Professional Services: https://CMOD.cloud

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

jeffs42885

Quote from: jose.arotinco on September 05, 2014, 04:46:09 AM
Justin,
Thanks for the reply, the features are:

Platform: Windows Server EE
RAM: 8GB
Expiration Type: Load
Record in each AG: approx 3500, there are about 10 AG with over 100,000 records

I had thought the expiration run everyday, but I see it will not be a good idea.

jeffs42885,
The loaded data are text files...sorry but I do not understand when you say 5x40, that you mean that ...?

did not know that the subject of serious expiration complicated, some other additional thing that can recommend me? With all the features mentioned can be given approximately how many hours can take?

Thanks




I think I meant to say "24/7" as in the process aka the "migrator" (custom script we got from IBM) was not being ran 24/7