Re: "Checkpointing long" on exit

> -----Original Message-----
> From: Steve Fiddle <[email protected]>
> Sent: Tuesday, March 16, 2021 10:14 AM
> To: Audacity-Devel list <[email protected]>
> Subject: Re: [Audacity-devel] "Checkpointing long" on exit
> 
> 
> 
> On Tue, 16 Mar 2021 at 14:22, Leland <mailto:[email protected]> wrote:
> > -----Original Message-----
> > From: Steve Fiddle <mailto:[email protected]>
> > Sent: Tuesday, March 16, 2021 8:25 AM
> > To: Audacity-Devel list <mailto:[email protected]>
> > Subject: [Audacity-devel] "Checkpointing long" on exit
> >
> > Why is this happening?
> >
> > Importing large WAV from hdd:
> > 1. Launch Audacity
> > 2. Drag and drop large WAV file (2.4 GB) from hdd into Audacity.
> > Import takes about 45 seconds.
> > 3. Exit Audacity
> > 3.1. "Save project before closing?" -> No
> > 3.2 "Checkpointing long" dialog opens and may take 30 seconds before
> > Audacity closes.
> >
> > Why is Audacity doing "checkpointing"?  What is it actually doing?
> >
> > If I wait a couple of minutes after the file has fully imported before exit,
> > Audacity closes immediately. Does this mean that Audacity is actually doing
> > part of the import process in the background after the waveform has
> > appeared?
> >
> > Importing from SSD:
> > 1. Launch Audacity
> > 2. Drag and drop large WAV file (2.4 GB) from SSD into Audacity.
> > Import is MUCH slower (around 1 minute 30) ???
> > 3. Exit Audacity
> > 3.1. "Save project before closing?" -> No
> > 3.2 Audacity closes immediately.
> >
> > Why does import from SSD take twice as long as from a much slower hdd?
> >
> 
> Checkpointing is done in a separate thread and when a database is closed, all
> checkpoints must complete before Audacity can continue.  In both of your
> cases, the checkpointing should be started while the file is still being
> imported.  But, in your first case, the checkpoints take longer to complete so
> there's more left to do when the database is closed at Audacity shutdown.  In
> your SSD test, the checkpoints seem to be finishing during the import and not
> delayed to database close.
> 
> Well, that's my first guess anyway.  A quick review of the code does seem to
> prove the theory, but reality may vary slightly.  😊
> 
> That's pretty much what I guessed, but it doesn't explain why importing from a
> fast SSD is much slower to display the waveform than when importing from a
> much slower hdd (as both Peter and I have observed and measured).
> 
> @ Peter, which drive is your Audacity temp folder on?
> 
> @ devel, could it be anything to do with the file being read and the project
> being written to being on the same drive?
> 
That would be my guess as well.  I have multiple SSDs and HDDs here and, if I can recreate the same thing you and Peter are seeing, I should be able to determine if the "same drive" theory is contributing to the problem.






_______________________________________________
audacity-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-devel