UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Before I release it, I will make sure that everything is working properly and then I will release it.
Hi,
I stack up to 2-3000 frames sometimes including saving calibrated frames so I can get plain alignment on one shot color cameras. So I start to run out of my internal solid-state drive space even though I have a 2 GB drive.
Niw I have an external hard drive that’s fairly fast (200mb/sec 14 Tb drive) so I’m trying to decide which of these two scenarios is faster:
1) keep all the source files and write the the calibrated frames on an external hard disk and use the internal drive only for the integration working storage.
or
2) keep all the source files and space for the calibrate frames on the internal solid-state drive and use an external hard disk for the integration working storage.
I’m assuming option number one would be faster because I’m expecting the integration working storage to be worked a lot harder and that the source files are essentially only read once or a small number of times. Is my assumption correct?
@readyjetty If you're looking for performance during processing then simply copy all files over to your internal drive, process using the internal drive and copy the results back to the external drive.
I guess I should’ve been more clear: My internal drive is a very fast NVMe 2 TB SSD and cannot be upgraded and all the files and stacking procedures requires more than that.
So I either need to put them all on an external hard drive or split them and I’m asking if I split them should I use the internal very fast NVNe SSD as the working file space or for the source files, because I can’t use it for both.
This is just my thinking for your situation. If you had a smaller stack, say 100 light frames, then the performance difference would probably go unnoticed either way. But considering you have up to 3,000 light frames to stack, I think you would see faster results if your light subs were stored on the SSD and you did the final integration to your external drive.
That is a lot of light frames that APP will have to access individually, so over the course of the entire process, keeping the light frames on the SSD would seem to work better. Then if my thinking is correct, APP would only have to write one integration file to your slower external drive.
