I cant seem to get timely post federation to my instance (moist.catsweat.com) from lemmy.world. I might see a new post every few hours instead of every minute or so.

posts from other lemmy instances (lemmy.ca, lemmy.ml, dbzer0, etc) have no problem.

i see a ton of lemmy.world traffic in my nginx logs… it seems very specific to ‘new posts’. voting/comments seem to come through no problem once the post shows up.

ive checked a few other instances similar to mine, and they are not having this issue. so it seems something specific to lemmy.world and my instance.

i do recall a similar issue several months back, and it involved a lemmy.world admin resetting some outbound queue.

any ideas?

  • Nothing4YouEnglish
    2•2 months ago

    Hi, I run this.

    What benefit do you expect from longer retention periods and how much time did you have in mind?

    The way data is currently collected and stored keeps the same granularity for the entire time period, which currently uses around 60 GiB for a month of retention across all monitored instances.

    • @[email protected]
      1•2 months ago

      Mainly, I’m interested in how Lemmy is growing and changing as a whole. If there was a way to store activity just weekly or even monthly that would help.

      • Nothing4YouEnglish
        1•2 months ago

        so all you’re looking for is the amount of activities generated per instance?

        that is only a small subset of the data currently collected, most of the storage use currently comes from collecting information in relation to other instances.

          • Nothing4YouEnglish
            2•2 months ago

            I’ll probably have to look at another storage than prometheus, aiui it’s not really well suited for this task.

            maybe something with influxdb+telegraf, although i haven’t looked at that yet.

              • Nothing4YouEnglish
                1•1 month ago

                do you happen to have experience with setting up influxdb and telegraf? or maybe something else that might be better suited?

                the metrics are currently in prometheus metrics format and scraped every 5 minutes.

                my idea was to keep the current retention for most metrics and have longer retention (possibly with lower granularity for data older than a month).

                the current prometheus setup is super simple, you can see (and older copy of) the config here.

                if you want to build a configuration for influxdb/telegraf that i can more or less just drop in there without too many adjustments that would certainly be welcomed.

                the metric that would need longer retention is lemmy_federation_state_last_successful_id_local.