vuryi.blogg.se

Virtualbox shared folder cache
Virtualbox shared folder cache











virtualbox shared folder cache

So, another measurement was done, which consisted into measuring the time to serve one complete page: $ time wget -pq -no-cache -delete-after real 0m13.393s These two URIs produce more or less identical content, JSON-formatted status info regarding our front-end and back-end applications, respectively.

virtualbox shared folder cache virtualbox shared folder cache

$ time wget -pq -no-cache -delete-after real 0m0.019s Some measurements were taken showing up that the problem seemed to be located in our front-end application, since the back-end was running properly: $ time wget -pq -no-cache -delete-after real 0m0.523s The problem arose when we noticed Rails was underperforming when running in the local development setup. Not only that, in all our other environments, we run the apps using Unicorn as a daemon, with more or less workers, while in this development environment, we run WEBrick within a screen session, just to simplify the load. So this development environment’s architecture and infrastructure is quite different from the ones we have in staging, pre-production, and, of course, production. In some cases, for feature availability, performance, and workstation power reasons, these apps, and their components run completely on this environment, but in other cases, we don’t run all the components in the virtual machine and we do use some components from the staging (we call it develop) environment, which is quite approximate to what we need.

virtualbox shared folder cache

Most of us at Devex, we use a specific setup of our apps into a VirtualBox machine so we can hold a local development version of our site and check how the new features integrate before to give the work as done. Two weeks ago, we noticed some performance issues with Rails in our development setup, while all our other environments, some much less powerful, were working with much better performance.Īfter confirming that no recent change caused this slow-down, and running some diagnostics and measurements to record the performance in some point, this took us on a small trip into some Ruby on Rails debugging on a VirtualBox.













Virtualbox shared folder cache