XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Won't fix
    • Icon: Trivial Trivial
    • None
    • 2.4.3
    • Server (S)
    • None
    • Production

      Hi,

      We are having issues where the DB is growing really fast lately, as we have been adding quite a few devices and collecting more DATA we have not been concerned however we found the following:

      The history Table seems to be the largest by far.
      We did a query on it:

      mysql> select FROM_UNIXTIME(clock) from history_uint where itemid = 57246 limit 20;
      +----------------------+
      | FROM_UNIXTIME(clock) |
      +----------------------+
      | 2012-11-24 09:04:13  |
      | 2012-11-24 09:05:13  |
      | 2012-11-24 09:06:13  |
      | 2012-11-24 09:07:13  |
      | 2012-11-24 09:08:13  |
      | 2012-11-24 09:09:13  |
      | 2012-11-24 09:10:13  |
      | 2012-11-24 09:11:13  |
      | 2012-11-24 09:12:13  |
      | 2012-11-24 09:13:13  |
      | 2012-11-24 09:14:13  |
      | 2012-11-24 09:15:13  |
      | 2012-11-24 09:16:13  |
      | 2012-11-24 09:17:13  |
      | 2012-11-24 09:18:13  |
      | 2012-11-24 09:19:13  |
      | 2012-11-24 09:20:13  |
      | 2012-11-24 09:21:13  |
      | 2012-11-24 09:22:13  |
      | 2012-11-24 09:23:13  |
      +----------------------+
      

      Since we have set the templates to only keep Data for at most 1 year:
      Actually for most we have :
      History storage period (in days) 30
      Trend storage period (in days) 365

      Can you please let me know if I am just understanding this wrong?

            Unassigned Unassigned
            craffop Peter Crafford
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: