I'm on a gigabit connection to the Perforce server, have plenty of RAM, multiple CPU's and only one CPU is being utilised. gah!

What I would like is to set in the Admin console the 'maximum concurrent index threads per repository', the current option to set '3' is fine if you have 3 repositories. I don't. This feature would potentially reduce the index time by a factor of how many CPU's I have (say 4). This feels like a relatively simple change (farm out a changeset index to another thread, update UI with status).

This would be a major performance improvement for installations with large repositories.