Even with my PC having a quite fast i7 6700K, RTB's 3DS Maxscript had similar times ranging from 5-10 minutes. I think that's just because MaxScript is not really performantly executed, it partly works on the slow 3DS Max GUI.
With my Blender add-on, working purely in memory, but being Python interpreted at runtime, I experience the following times (It depends on the input, since you can also decompress SZS compressed BFRES files on the fly):
- Uncompressed BFRES character: 2 seconds
- Uncompressed BFRES track: 20 seconds (texture decompression with TexConv is the slowest part of this)
- Compressed SZS character: 10 seconds
- Compressed SZS track: 1 minute
As you can see, SZS is quite a bottle neck. I can't do it faster with raw Python, and already optimized it together with some professionals. If you need it faster, you should decompress SZS with an external tool (to which in some future version the work can probably be delegated to to speed it up for Blender too).
With my Blender add-on, working purely in memory, but being Python interpreted at runtime, I experience the following times (It depends on the input, since you can also decompress SZS compressed BFRES files on the fly):
- Uncompressed BFRES character: 2 seconds
- Uncompressed BFRES track: 20 seconds (texture decompression with TexConv is the slowest part of this)
- Compressed SZS character: 10 seconds
- Compressed SZS track: 1 minute
As you can see, SZS is quite a bottle neck. I can't do it faster with raw Python, and already optimized it together with some professionals. If you need it faster, you should decompress SZS with an external tool (to which in some future version the work can probably be delegated to to speed it up for Blender too).