Hi Folks
It seems since upgrading to MODX (2.6.4),
Vapor no longer does what it's supposed to.
My I/O Usage and Physical Memory Usage simply go through the roof,
eventually ending up in a timeout.
After fiddling around for too long I ended up contacted my host
who helpfully supplied the following feedback...
"The I/O and RAM usage spikes around the same time as the following files were created or modified:
2018-06-11 12:27:35.0570217140 ./mySite.com/vapor/model/vapor/vaporvehicle.class.php
2018-06-11 12:27:35.0570217140 ./mySite.com/vapor/scripts/resolve.extension_packages.php
2018-06-11 12:27:35.0580217140 ./mySite.com/vapor/scripts/resolve.media_source.php
2018-06-11 12:27:35.0580217140 ./mySite.com/vapor/scripts/resolve.vapor_model.php
2018-06-11 12:27:35.0590217140 ./mySite.com/vapor/.gitignore
2018-06-11 12:27:35.0590217140 ./mySite.com/vapor/scripts/validate.truncate_tables.php
2018-06-11 12:27:35.0600217140 ./mySite.com/vapor/changelog.md
2018-06-11 12:27:35.0600217140 ./mySite.com/vapor/readme.md
2018-06-11 12:27:35.0600217140 ./mySite.com/vapor/vapor.php
If this script was updated at 12:27 I'd recommend rolling back the update -
If this script was first installed at 12:27 I'd recommend getting in touch with
its developers to see why it is using so much RAM and I/O"
Any clue would be appreciatively accepted
Many thanks
My setup:
MODX latest (2.6.4)
MAMP (4.3)
PHP (7)
MySQL (5.6.38)
Chrome: Safari: FF (latest versions)
MacOS Sierra 10.12.6
