Author Topic: WeatherCat memory usage  (Read 4747 times)

Blicj11

  • Storm
  • *****
  • Posts: 4078
    • EW3808
    • KUTHEBER6
    • Timber Lakes Weather
  • Station Details: Davis Vantage Pro2 Plus | WeatherLinkIP Data Logger | iMac (2019), 3.6 GHz Intel Core i9, 40 GB RAM, macOS Sonoma 14.8.5 | WeatherCat 3.3.3 | Supportive Wife
WeatherCat memory usage
« on: April 12, 2016, 12:17:43 AM »
I have been watching WeatherCat 2.2x memory usage in my Activity Monitor. On a new start of WeatherCat, it takes up less than 200 MB for a short while and then progresses to between 200 and 275 MB. At the end of the month/first of the next month, WC memory climbs to over 300 MB. When I use the Data Viewer/Editor tool, even if I am not editing, just looking, usage climbs to well over 500 MB.

I draw no conclusions; I am just sharing what I observed.
Blick


elagache

  • Global Moderator
  • Storm
  • *****
  • Posts: 6686
    • DW3835
    • KCAORIND10
    • Canebas Weather
  • Station Details: Davis Vantage Pro-2, Mac mini (2018), macOS 10.14.3, WeatherCat 3
Month transition use is caching. (Re: WeatherCat memory usage)
« Reply #1 on: April 12, 2016, 11:41:37 PM »
Dear Blick and WeatherCat memory "dieters,"

I have been watching WeatherCat 2.2x memory usage in my Activity Monitor. On a new start of WeatherCat, it takes up less than 200 MB for a short while and then progresses to between 200 and 275 MB. At the end of the month/first of the next month, WC memory climbs to over 300 MB. When I use the Data Viewer/Editor tool, even if I am not editing, just looking, usage climbs to well over 500 MB.

I draw no conclusions; I am just sharing what I observed.

Sorry, I'm too late in the day to try all your experiments.  I'll try though since I can graph WeatherCat memory use.  I'm curious to open up the Data Viewer/Editor and see what that does.

I have the explanation for the increase in memory use in the transition between months.  Stu has WeatherCat keep the caches from the previous month while it starts caching data from the new month.  So for a while it has both months cached to improve data query time.  To get rid of the previous month cache just restart WeatherCat.

Cheers, Edouard

Blicj11

  • Storm
  • *****
  • Posts: 4078
    • EW3808
    • KUTHEBER6
    • Timber Lakes Weather
  • Station Details: Davis Vantage Pro2 Plus | WeatherLinkIP Data Logger | iMac (2019), 3.6 GHz Intel Core i9, 40 GB RAM, macOS Sonoma 14.8.5 | WeatherCat 3.3.3 | Supportive Wife
Re: Month transition use is caching. (Re: WeatherCat memory usage)
« Reply #2 on: April 13, 2016, 01:34:10 AM »
I'm curious to open up the Data Viewer/Editor and see what that does.

I have the explanation for the increase in memory use in the transition between months.  Stu has WeatherCat keep the caches from the previous month while it starts caching data from the new month.  So for a while it has both months cached to improve data query time.  To get rid of the previous month cache just restart WeatherCat.

The only thing I have done any different is open up the Data Viewer/Editor while I was testing Apple Scripts on this build. I just did it again. I ran one script and then I bounced around in the Viewer, going through about 10 dates. WeatherCat went from 551 MB to 643 MB.

Thanks for the more detailed explanation on month-end caching. I knew it was doing something at the beginning of a new month but didn't know exactly what.
Blick


elagache

  • Global Moderator
  • Storm
  • *****
  • Posts: 6686
    • DW3835
    • KCAORIND10
    • Canebas Weather
  • Station Details: Davis Vantage Pro-2, Mac mini (2018), macOS 10.14.3, WeatherCat 3
Need to try Data Viewer again. (Re: WeatherCat memory usage)
« Reply #3 on: April 14, 2016, 12:04:03 AM »
Dear Blick and WeatherCat memory "dieters,"

The only thing I have done any different is open up the Data Viewer/Editor while I was testing Apple Scripts on this build. I just did it again. I ran one script and then I bounced around in the Viewer, going through about 10 dates. WeatherCat went from 551 MB to 643 MB.

Okay, I'll have to make another test on this.  I just opened the Data Viewer/Editor and left it open while having breakfast.  That wasn't enough to change the memory use at all.  I'll try again with some use and see if I can reproduce this.

Cheers, Edouard