-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Light resource use on new Mac Pro, but heavier resource use on older Mac Pro #25
Comments
Moreover, now I'm wondering if it is working right... I just noticed this if I am manually starting the gatling ... so say I up my vagrant, then hit ctrl-c and do something, then start the gatling-rsync-auto again.
Ok... so it does this "watching" thing. And just sits there using no real CPU time to worry about. Great. Then I change one file in one place. Save. It triggers a new rsync... and another... and another...
After that first "watching" wait that occurred, I never see it "watch" or wait again. And so I had not really noticed this when it was launching automatically at "up" time. Is it supposed to constantly run the rsync over and over and over even if no file changes have been made? |
same problem here
it used to be around 3s or better, under 1s for a while number of files
|
this plugin trigger vagrant rsync. rsync process includes creating ssh connection.
this idea leads me to https://gist.github.com/jedi4ever/5657094 then
and eventually
i don't understand why when i delete configuration for dns in my Vagrant file and then reload the machine, ssh connection is still quick. however, this is a different story. |
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.
The text was updated successfully, but these errors were encountered: