Performance Decrease If Left Open For A Long Period

[dshastry]

I've been noticing an issue with Scout as I go to generate my SCSS files recently. Since I do a ton of FED, I usually leave Scout running in the background to compile my SCSS across a bunch of different projects. When I start the app, generation times are around 2-350ms, but over the course of the day the times steadily keep creeping up, sometimes taking over two seconds to compile.

I assumed this was just because my files are getting larger so there's more to compile, however, if I quit the app, wait a second or two and then relaunch, it will go back to generating like it was previously around 300ms. I've noticed this performance behavior across the two Macbook Pros and one MacMini that I have at the office so I'm sure its not machine dependent (also the MBP's are the latest gen so I know system processing power isn't the bottleneck either).

Any idea why this is so? Something to do with an app cache getting full after multiple generations, perhaps?

[TheJaredWilcurt]

I'll have to look into this. It's not something I've tested for, so I'm not sure what is occurring. Probably some cache building up or not being cleared. I'll be curious if it's something I have control over. More than likely this is being caused by one of Scout-App's dependencies:

• Node-Sass which handles reading files, handing them off to LibSass, and returning the data from LibSass
• LibSass itself which actually processes the data handed to it by Node-Sass and returns CSS data to Node-Sass
• Chokidar which monitors for file changes and then has Node-Sass do it's thing

[dshastry]

Sounds good @TheJaredWilcurt. Let me know if I can provide insight by providing a dump or log of any kind.