If you are copying a lot of files to a compressed path, the background compression system will tend to lag behind. That is, ZipStream will have many outstanding compression tasks not yet completed. There is no problem with this, as this is the way ZipStream is designed to operate. You may look at files and see that they are not compressed yet. This is quite normal, as the compression operation needs time to catch back up. We highly recommend that you use the ZipStream Monitorprogram so that you can be aware of the background operations taking place.
Note: You can use the files immediately even thought they are still queued for compression.
When the background compression operation gets well behind, it will attempt to rectify this situation by boosting its own priority slightly. This means that you may notice a small drop in system performance as ZipStream tries to catch up.
If you need the outstanding compression operations to complete in the shortest possible time, you can use the ZipStream Syncutility to provide a significant boost to the background compression priority.