How much extra disk space is required for chat?

[th21]

Will chat messages take a significant amount of disk storage? I have roughly 15G remains and around 100 active users per day and would like to test it.

[mcwumbly (Dave McClure)]

Hey @th21 apologies for the delayed response here!

I don’t think you should be too concerned about disk space. On one or the most active chat forums we host, this is the breakdown of current disk space usage for various database tables:

| 754 MB     | posts                |
| 511 MB     | post_search_data     |
| 471 MB     | uploads              |
| 410 MB     | post_timings         |
| 336 MB     | stylesheet_cache     |
| 258 MB     | user_auth_token_logs |
| 251 MB     | user_actions         |
| 199 MB     | post_hotlinked_media |
| 117 MB     | notifications        |
| 109 MB     | chat_messages        |
| 105 MB     | user_histories       |
| 104 MB     | post_actions         |
| 100 MB     | topic_links          |

This site uses the default 90-day retention period for messages in chat channels, and unlimited retention for direct messages.

In any case, I doubt it’ll be an issue for you, and you an existing option to mitigate the risk by lowering the retention period if you do find it to be an issue.

Hope that helps!

And if you do start trying it out or have already done so, we’d be happy to hear any other feedback you have here or in the #chat-feedback channel.

[th21]

Ty for the detailed table, can I ask how to get one if I would like to check my forum’s space breakdown as well?

[mcwumbly (Dave McClure)]

That’s not something I have direct experience doing, but here is an older answer form another topic:

@tgxworld

You can run the following commands to see which tables are taking up the most disk space

./launcher enter app
su - postgres
psql discourse

SELECT nspname || '.' || relname AS "relation",
    pg_size_pretty(pg_total_relation_size(C.oid)) AS "total_size"
  FROM pg_class C
  LEFT JOIN pg_namespace N ON (N.oid = C.relnamespace)
  WHERE nspname NOT IN ('pg_catalog', 'information_schema')
    AND C.relkind <> 'i'
    AND nspname !~ '^pg_toast'
  ORDER BY pg_total_relation_size(C.oid) DESC
  LIMIT 20;