For all I know your machine has lots of RAM and you've 10 other environments running in the background. I know it's frustrating, and your main reason for using local dev environments is it's faster than developing in production (there are many other good reasons to use local dev), but I don't think you have realistic expectations, and there are so many unknown variables. remote requests, your computer isn't in a data centre on an internet backbone so of course a request to Instagram will be much slower than from say a SiteGround or GoDaddy server, if only because there's a greater number of hops, eitherway it's bad on all hosts ). Fundamentally though, you have yet to actually identify what is slow beyond a Product name, except in scenarios where I would expect it to be slow for any or all hosts purely because of the way it was done ( e.g. I know you want it to be just as fast, but you are at the mercy of what the code does, and the local hardware available to you. You will never get identical performance to a remote host, or even between remote hosts, and the chances of a complete refresh uninstalling VirtualBox Vagrant etc changing this are low in the extremes. Some themes are faster than others, and they're faster or slower for different reasons. Others don't have good network connections ( or antivirus and firewalls that meddle with it ). Avada will be doing things other themes don't, those might not play to the strengths of your local machine.įor example, some users take a very long time to provision VVV due to spinning mechanical disks. They all have things they excel or not excel at, much like some cars have better torque, some have better breaks, some are faster, some are more efficient.
VVV performance is not linear, nor is any other host. There are faulty expectations at play here. Of course switching from a default theme to Avada will make things slower. I just created a new VVV site from scratch, and began to experience the same issue, this time after installing the Avada theme. Treat it like an Onion, you've built layers up, so tear them down in the right order, don't start at the foundations first, it's messy
vagrant destroy lets Vagrant do all the cleanup it needs, but by removing VirtualBox first, you mess with that. These steps are a tad over the top, and a bit like removing the bottom 2 layers of a Jenga tower, it's anything but clean ( which appears to be your goal. Uninstall VirtualBox (since this will carry out a vagrant destroy).
0 kommentar(er)
