0
Hi, Everything is working really well on my 'test' installation. Albums, artists, mp3s and cover scans, all perfect.
Today I have just loaded 35,000 albums and 10,000 artists into the mysql database.
The 'admin' Music Collection/Albums form stopped working until I increased the php memory size to 64mb.
Also the front end and admin slowed down a fair bit LOL.
Could you advise me on any suggestions on how to speed up performance or reduce the memory requirements?
Would it be possible to separate the 'images' from jos_muscol_albums in the same way that 'songs' are in a different table?
Jos_muscol_albums on my test system is already 6.3mb, I have another 50,000 albums still to add and then 80,000 images LOL.
I'd be grateful for any advice.
Thank you
Rand.
Today I have just loaded 35,000 albums and 10,000 artists into the mysql database.
The 'admin' Music Collection/Albums form stopped working until I increased the php memory size to 64mb.
Also the front end and admin slowed down a fair bit LOL.
Could you advise me on any suggestions on how to speed up performance or reduce the memory requirements?
Would it be possible to separate the 'images' from jos_muscol_albums in the same way that 'songs' are in a different table?
Jos_muscol_albums on my test system is already 6.3mb, I have another 50,000 albums still to add and then 80,000 images LOL.
I'd be grateful for any advice.
Thank you
Rand.
Responses (2)
-
Accepted Answer
0well, first of all.. thats a quite large collection! it is normal that things speed down a little bit.
suggestions: if you had to increase the memoery size, maybe thats because you were trying to see a list with ALL artists on the backend... is that possible? in any case, first suggestion: never choose "All" on backend pagination, but some finite number... 50, 100.. what you like more.
on the frontend: use pagination!!! Music Collection is prepared to enable/disable pagination on frontend artists view. thats a paramter of MC, called "use pagination on artists view". set it to YES
no, images cannot be separated from the album table.. (anyway, that wouldn't speed things up, because only the image name is stored on the databse, not the image itself, so no need to do that)
dont worry for the images, they are NOT stored in the database.
anyway, all I can say is the same I said before... this is a quite large collection so its normal that it slows querys a little bit. in any case this is a "limitation" of MySQL and not MC's.
but anyway, I think MySQL is ready to manage laaaaaarge amounts of data! (much more large than 6,3Mb, I think) -
Accepted Answer
Your Reply
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »