I'm using Storage Emulator v 3.2 and I've just uploaded about 370.000 blobs totalling some 75GB. Now I'm experiencing constant CPU usage of between 35-40% by the emulator process just by doing nothing (i.e. not actively using the emulator).
Does anyone know what the emulator is doing "when it's not doing anything"? Is it doing some sort of indexing or anything? Would the constant CPU usage have something to do with the large number of files (if 370K files is considered large anyway) or large amount of storage used?
The emulator is not built for scale and it is possible that the large number of blobs is causing the garbage collecting component to take a long time and consume CPU. We will look at improving the efficiency of the garbage collector in the future. In the meantime, reducing the number of blobs stored in the emulator should improve this.