Slow Emby after symlink-ing appdata

[denywinarto 5]

I know it isn't advised, but i symlink'ed my emby to another drive due to backup and C size reasons,

But then when i open emby from another network, it's terribly slow and wont load at all

is there any other way to move it safely to another drive?

Storing it in C is not very practical in my opinion..

Edited September 5, 2018 by denywinarto

[Luke 42078]

Hi there, I wouldn't suggest doing this. What drive did you move it to?

[denywinarto 5]

Stored it in a jbod + drivepool consisiting multiple 12 tb drives, i jave set the cache on the main ssd drive but it doesnt seem to make much difference..

 

At least emby should let user store growing metadata on another drive i think

[Luke 42078]

Have you explored the settings in emby server that allow you to configure various paths?

[denywinarto 5]

Have you explored the settings in emby server that allow you to configure various paths?

 

Ok so i reverted it back to C, and i set the metadata to my drivepool from advanced settings..

Doesn't seem to make much difference from client..

It could be because my library is huge (100TB)

But i swear it wasnt this slow before i sym link'ed it...

 

What if i put another NVME drive, and then move entire emby folder to it. 

Would there be any performance difference?

And if symlink is not allowed... then does emby allow installing on different drive?

Edited September 14, 2018 by denywinarto

[Luke 42078]

 

 

Would there be any performance difference?

 

I don't know. Depends on which drive is faster.

[Luke 42078]

The next release of the server will perform considerably faster. You can follow that here:

https://emby.media/community/index.php?/topic/61079-3603-db-changes/

 

Thanks.