response time

Richard's Avatar

Richard

10 Aug, 2018 03:20 PM

My library atm has 87k tracks. (Windows 8.1 PC, folder-based library, beaTunes 5.1.8.) The h2.db file was 840 MB. Now I've been analyzing my tracks, calculating BPM, color, mood, key, electric/acoustic marker, danceability (from online source), lyrics, and creating the fingerprint. I'm about 25,000 tracks into it. Using all 4 cores on my 4-year old i5, it's processing about 1,000 tracks per hour, which is fine. The h2.db file is now up to 1135 MB. It was kind of funny: After I processed about 5000 tracks, the h2.db didn't grow at all (according to file explorer). Now's it's jumped up in size by quite a bit.

My question is on response time. When the h2.db file was 840MB, I was noticing that the response time between when I right-clicked on a track to bring up the context menu and when the menu came up was running around 12 seconds at best for many tracks. So, about a 12 second lag in order to do anything with the file, like play it. This was on a quiet system. The db file is on my SSD. The tracks are on a separate internal HDD. Is this response time to be expected?

I'm concerned what my response time will be when I add my other 270,000 tracks to the library from their root folder.

I paused the analysis now and tried again. Just hitting "enter" on a song title generated a "Failed to open item" error. (attached screen cap). I find if I left click on a file name, then right click to bring up the context menu, sometimes it's pretty fast (1-2 seconds), sometimes I have to repeatedly right-click (up to 15 seconds or so).

  1. Support Staff 1 Posted by hendrik on 13 Aug, 2018 04:32 PM

    hendrik's Avatar

    Response time for the context menu should never be this long.

    Could you please reproduce the issue, perhaps even multiple times, and then upload your logs via `Help` -> `Upload Logs`. I'd like to see what's taking so long.

    Thanks!

  2. 2 Posted by Richard on 13 Aug, 2018 06:00 PM

    Richard's Avatar

    I've done some more testing.  It seems that the order I do things makes a difference.

    If I scroll down to a random song and then right-click, the context menu comes up right away.

    If I scroll to a random song, left-click to highlight it, and then right-click, sometimes the right-click is ignored and nothing ever happens. Sometimes, it takes 12 seconds or so for the context menu to come up. And sometimes the context menu pops up right away. Sometimes if I left click, wait about 3 seconds, and then right click, the context menu comes up right away. It seems as if beaTunes has to "get going". Usually, the delayed responses are happening only the first handful of times I try to access a tune. After that, things are much faster.

    So, maybe the problem (if there even is a problem) works itself out after a few minutes or after a few file accesses.

    I'm content to close this issue unless something changes. Thanks for your time on this. Sorry to raise a false alarm.
    I'll still upload the logs in case you want to look at them.

          From: hendrik <[email blocked]>
     To: [email blocked]
     Sent: Monday, August 13, 2018 11:32 AM
     Subject: Re: response time [Questions #9929]
       
     #yiv6581907069 pre {width:92%;margin:10px 2%;padding:5px 2%;background:#efefef;border:1px solid #d6d6d6;}#yiv6581907069 blockquote {margin-left:0;padding-left:1em;border-left:5px solid #ccc;}

  3. Support Staff 3 Posted by hendrik on 14 Aug, 2018 04:20 PM

    hendrik's Avatar

    Thanks for the logs and the improved description.

    The issue probably only happens when you select a song in a *large* playlist (e.g. the main library) and then right-click right away. When you do the same in a *short* playlist, you cannot observe the issue. Correct?

    I have looked at your logs and there is indeed something that is worth speeding up. I'll try to get an improved version to you in the next couple of days.

  4. 4 Posted by Richard on 14 Aug, 2018 05:26 PM

    Richard's Avatar

    I won't have time to do any testing today. I don't have any playlists created except for the main library, so I can't speak to your question on that. I never noticed a problem of this type when I was working with much smaller libraries.

          From: hendrik <[email blocked]>
     To: [email blocked]
     Sent: Tuesday, August 14, 2018 11:20 AM
     Subject: Re: response time [Questions #9929]
       
     #yiv9218529326 pre {width:92%;margin:10px 2%;padding:5px 2%;background:#efefef;border:1px solid #d6d6d6;}#yiv9218529326 blockquote {margin-left:0;padding-left:1em;border-left:5px solid #ccc;}

  5. Support Staff 5 Posted by hendrik on 15 Aug, 2018 02:38 PM

    hendrik's Avatar

    Hey Richard,

    I have managed to implement the change I've mentioned. If you want to try it out, please shut down beaTunes, then download https://www.beatunes.com/download/beaTunes-5-1-9-SNAPSHOT-x64.exe and run the installer.

    Hopefully that made the context menu appear faster.

    Thanks,

    -hendrik

  6. 6 Posted by Richard on 15 Aug, 2018 04:28 PM

    Richard's Avatar

    That is a LOT faster. Context menu pops up in approx 1 second or sub-second response. Thank you so much for finding and implementing that solution.

          From: hendrik <[email blocked]>
     To: [email blocked]
     Sent: Wednesday, August 15, 2018 9:38 AM
     Subject: Re: response time [Questions #9929]
       
     #yiv5232256141 pre {width:92%;margin:10px 2%;padding:5px 2%;background:#efefef;border:1px solid #d6d6d6;}#yiv5232256141 blockquote {margin-left:0;padding-left:1em;border-left:5px solid #ccc;}

  7. Support Staff 7 Posted by hendrik on 15 Aug, 2018 06:42 PM

    hendrik's Avatar

    Thanks for reporting this and being willing to try out the snapshot!

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac