Every time you run zmprov or zmmailbox, it has to crank up a new JVM thread which is a lot of overhead; however, you can run it in batch mode.
ie: It would be better to aggregate a list of actions and then send them all to one instance of zmprov:
Quote:
nano /tmp/script.sh Code: #!/bin/bash
COUNTER=0
while [ $COUNTER -lt 30000 ]; do
echo "ca testing$COUNTER@domain.com password" 1>>/tmp/provision.txt
let COUNTER=COUNTER+1
done chmod 744 script.sh
./script.sh
zmprov < /tmp/provision.txt
|
Or zmprov -f /tmp/provision.txt
Infact it may be faster to do it via LDAP directly (zmprov -l < provision.txt) instead of mailboxd/Java/SOAP; though I haven't done an analysis in this case - some commands will need to talk to the mailbox server anyways.
Just ran it on a vm with 512mb ram ~1ghz proc dedicated to it (ZCS 6.0.0 D2, all default settings, no Java/LDAP tweaks):
- Less than 30sec to make the .txt
- Creates roughly 10k accounts every 10 minutes (ran zmaccts every so often in other terminal)