Why is Umami only ever showing just over 8 Kb disk usage?
-
I suspect I’m wrong here but I thought the disk usage displayed by each app typically included the database disk usage too, not just files underneath the app. In my case I never see Umami disk usage ever above 8.19 Kb of disk usage which just seems “wrong” to me. Am I misunderstanding something about how either Cloudron? disk usage works or how Umami stores its data?
As an example, my Matomo app (similar use case as Umami) is showing 60.95 Mb and I believe I’ve seen that change sizes occasionally, as opposed to Umami.
Would love some insights.
-
The diskusage for an app is indeed only the disk usage of files the app stores in /app/data
The databases are shared across apps and so they are stored elsewhere on the system. I get the use-case for this though but I am not sure how easily this can be supported to figure out which table/collection in the database services amounts for how much disk space used.
-
@nebulon it can be gleaned from backup DB dumps
-
@nebulon thank you for the answer. I guess I’ve been wrong this whole time thinking the DB usage was included.
Assumed maybe there was something wrong with my Umami instance. I think it would be nice to see the database usage in each app, because in the case of Unami for example it then makes it look like it’s consuming next to nothing when over a longer period of time with many websites maybe upwards of several hundred megabytes or more of database usage for example which is sort of “hidden” away when determining the full system impact of each app. -
@robi said in Why is Umami only ever showing just over 8 Kb disk usage?:
@nebulon it can be gleaned from backup DB dumps
I think for the correct size one has to get this information from the database. Atleast, the mysql/postgresql dumps we generate are unrelated in size to the actual size on database. I guess each database has it's own mechanism to determine a database's size.
