Problem scanning huge source (mem leak)?
#29
Can give some positive feedback. With a clean SD-card (LE 7.95.3) scanning is now at 100k songs with 135MB DB. No unplayed song queries, no mysql-slow errors!! Laugh

Scanning speed isn't glorious, but not that slow as expected:
Code:
06:44:39.754 T:1763701664   DEBUG: Mysql commit transaction
06:44:52.128 T:1763701664   DEBUG: Mysql commit transaction
06:45:04.151 T:1763701664   DEBUG: Mysql commit transaction
06:45:16.227 T:1763701664   DEBUG: Mysql commit transaction
06:45:28.227 T:1763701664   DEBUG: Mysql commit transaction
06:45:40.930 T:1763701664   DEBUG: Mysql commit transaction
06:45:52.821 T:1763701664   DEBUG: Mysql commit transaction
06:46:04.248 T:1763701664   DEBUG: Mysql commit transaction
06:46:17.282 T:1763701664   DEBUG: Mysql commit transaction
06:46:19.473 T:1763701664   DEBUG: Mysql commit transaction
06:46:21.399 T:1763701664   DEBUG: Mysql commit transaction
06:46:23.557 T:1763701664   DEBUG: Mysql commit transaction
06:46:34.568 T:1763701664   DEBUG: Mysql commit transaction
06:46:46.117 T:1763701664   DEBUG: Mysql commit transaction
About 12s per album

It feels like really these queries were the reason. Memory is slowing filling up during scanning, but somehow recovers again
Reply


Messages In This Thread
RE: Problem scanning source - by DaveBlake - 2017-02-12, 13:00
RE: Problem scanning source - by Uatschitchun - 2017-02-12, 21:51
RE: Problem scanning source (mem leak)? - by Uatschitchun - 2017-02-16, 09:05
Logout Mark Read Team Forum Stats Members Help
Problem scanning huge source (mem leak)?0