Technically speaking, it'd be interesting for the dev team to run a testnet simulation to check anonymity and bloat scaling impact, as well as spam attack vectors against the blockchain.
There were performance tests mentioned in section 5 of the whitepaper:
5. Performance
5.1. Proof Sizes
The affine coordinates are 64 bytes per ring member per coin value.
We store the public key or keyImage, which is 33 bytes
That leaves us with ~97 bytes ring member input
5.2. Benchmarks
The following benchmarks were done on an Intel(R) Core(TM) i73537U CPU @ 2.00GHz
with 8GB of RAM, using the average times out of 300000 iterations:
Algorithm Ring members Average Time Average time ring member
Signing 200 449ms 2.25ms
Verification 200 440ms 2.2ms