Good morning,

that is the classic answer, well it depends.  You say average hardware but there are a ton of variables that come into play.

cpu, number of cores, disk type, response time of disk etc.

Also, independent of the underlying infrastructure supporting the hypervisor, what about the disk setup for retain?  

All on one drive, several?

database, do you have that on separate disk and segregated across disk or disks?  When i say disks, i am referring to drives.

also the VM’s themselves.  Number of cores and cpu allocated

SAN connection assuming fiber or 10GBs, 40Gbs or?

this is somewhat borderline support question that can be checked against Config’s we have seen.  There should be a little more dialog to help get you to where you want to be.

Hi David,

I am getting 1-2 messages per second with the PAM tool, a 65,150 user archive is 10gb and is going to take about 6.5 hours. We have VMware with enough RAM on every guest that there is no swapping and fiber channel that I have seen with ATTO run at 800 megabytes per second.  The import is so slow we could have 10 sites with multiple PAM sessions over a WAN and the bottleneck would NOT be the WAN.  Something is wonky and very slow and I do not know how to pinpoint it.

It may have to do with the RETAIN system trying to do DEDUPE on every message as the message is presented.  It should be that the batch is pumped to the server and at night or the weekend have a task that de dupes.  Like a staging table where the first stage is stored and NOT de duped so that it can get the process done and then have a sub process finish.  In human terms RETAIN has one stomach to process all the food where us sophisticated humans have a stomach, small and large intestines. LOL

Joe,

Retain doesn´t do depud after archiving, but during the job. Every message get hash and this hash is compared with already stored messages during archive job. Maybe this what is slowing down the whole process.

I have customer with 100 users and the speed isn´t much different from customer with 2 000 users. 

Joe,

Retain doesn´t do depud after archiving, but during the job. Every message get hash and this hash is compared with already stored messages during archive job. Maybe this what is slowing down the whole process.

I have customer with 100 users and the speed isn´t much different from customer with 2 000 users. 

It needs to be user selectable, at least on the PAM import.

Is this on the roadmap or a future version?

Does MicroFocus use RETAIN, i.e. do they dog food the software?  The system managers must hate retain because of this issue.  You can only support x users as they want to archive x messages per day and it takes 1 second per message and after that we can start the backup. LOL