-
Notifications
You must be signed in to change notification settings - Fork 15
Description
My work machine is a 2013 Mac Pro (the tube thing). As stated by the project description, when gatling is running, it really has little CPU impact on that machine. It is great
On my 2008 Mac Pro at home, the CPU is generally stuck no lower than 20% utilization when gatling is running. I am guessing that this might have something to do with higher CPU overhead for older disk controllers? Or other inefficiencies?
The older Mac Pro at home has conventional magnetic disk drives, and the one at work uses SSD storage.
The older Mac Pro at home has less RAM (10gb) compared to the 16gb I have at work.
Aside from the hardware, the software versions are the same... same OS level, same VMWare Fusion, same Vagrant, same Git, etc. I disable antivirus before enabling any of these auto-rsync types of things, so it shouldn't factor in, either. That said, same AV software and version at work and home.
If I understand event coalescing, it is not the same as simply turning down the frequency with which gatling runs... I don't mind it triggering 1 second after a file change is event is raised, but I would be interested in being able to turn down the overall frequency from checking constantly to, say, every 5 seconds or so. I am wondering if it currently just runs too fast for my old home system to keep up with painlessly.