I'm sure you are doing this, but make sure your bundle is always up-to-date. Somehow, the versions of Ruby / Rails / etc were not compatible with one another, and they also did not give me error messages I could always chase down. I have had this problem on FreeBSD, and here was my solution. This might be more of a suggestion than an answer, because I don't know if it covers your issue, but it takes just a few minutes, and you might want to try it. There's a lot of different things that can cause your machine and apps to slow down, and you haven't really given us a lot to work with, so those are some general ideas of what I'd look into. A MacBook Pro's hard disk is designed for battery efficiency, not high performance, so if you're hitting the disk hard with a lot of database I/O, you could be heating the machine up and causing the apps to wait due to record locking or some sort of contention. How much RAM do you have? Maybe your apps are running low and having to swap out too much? That would affect your overall system performance making the CPU work harder, causing it to heat up. If you have periodic tasks it's performing you should see those cause the CPU activity to spike again then drop when the task ends. Use top -o cpu and watch to see if the highest load is the app you ran or maybe something else the app is causing to run.Ī Rails app will spike when it starts up but should settle down as it waits for incoming connections. Have you tried opening a terminal window and running top, or opening Activity Monitor, then running each one individually and seeing when your CPU starts to climb? Both top and Activity Monitor will let you sort by the CPU load an app is generating.
0 kommentar(er)
