large number of files.

[w3man 0]

How does emby handles large numbers of files?  Does emby use a database or just files for the metadata? 

 

 

[ebr 16178]

We have a database and multiple levels of caching.

 

What you consider "large" though can vary quite a bit.

[w3man 0]

I consider large of having 2000 movies plus around 30,000 tv episodes.  I just want to know to if I need to change my file system (linux) to ensure I do not run out of inodes.

[ebr 16178]

The underlying file-system limits shouldn't be a problem (other than within your own management of your media) and we have a number of users with libraries that large and larger.

[Happy2Play 9780]

Your biggest concern will be folder structure, but Emby is very flexible.  You can see more information here.

[TolkienBard 58]

I consider large of having 2000 movies plus around 30,000 tv episodes.  I just want to know to if I need to change my file system (linux) to ensure I do not run out of inodes.

Emby can handle a library that size with no difficulty whatsoever. I'm running a library about 25% larger than that and there are no issues to speak of in terms of indexing and the library. I do allow all metadata to be saved in the various media folders, but beyond that, I let the cache do its thing as far as making quick work of browsing and I run as smooth as can be. Any troubles I have had have been operator error, or developmental issues (such as HW transcoding), and that has nothing to do with library size.

[PenkethBoy 2068]

copes fine with  my TV and Movies plus over 500k of photos with no noticeable lag

 

makes the db approx 2gb in size though