locoDog
depends on tagging, cueing, file count, file path structure, too many variables
30MB is a reasonable size for a 30k+ track count,
Also how vdj writes to the database quickly, lets say you have a track and it takes up 1000 chars, then you add 1 more char in a tag, it will take that 1000+1 chars and write it on the end of the database, the 1000 chars where it was gets filled up with space char [because it would be slow to nudge everything after that entry back]
I know the backup procedure cleans up these space chars, maybe there's something done with at other points too, but blank lines are skipped over when performing database stuff.
30MB is a reasonable size for a 30k+ track count,
Also how vdj writes to the database quickly, lets say you have a track and it takes up 1000 chars, then you add 1 more char in a tag, it will take that 1000+1 chars and write it on the end of the database, the 1000 chars where it was gets filled up with space char [because it would be slow to nudge everything after that entry back]
I know the backup procedure cleans up these space chars, maybe there's something done with at other points too, but blank lines are skipped over when performing database stuff.
Posted Wed 26 Jun 24 @ 10:14 am
kradcliffe
Have you ran the database clean to see if it reduces the size?
Posted Wed 26 Jun 24 @ 10:17 am
Matty1000
kradcliffe wrote :
Have you ran the database clean to see if it reduces the size?
you mean "remove missing files" ? or is there another clean database option?
Posted Wed 26 Jun 24 @ 10:52 am
kradcliffe
No that's the one.
Posted Wed 26 Jun 24 @ 11:09 am