High CPU usage, question about RAM

1

Hello @duncan, I am getting consistently high CPU usage. I recently upgraded to Tahoe and I cannot recall if CPU usage was this high before.

Of note, I’m using an Intel MacBook Pro with 32GB of RAM. I am considering getting a new MacBook M5 and have a couple of questions:

  1. Would an Apple Silicon CPU make that much of a difference (other than it’s obviously 7 years newer and faster)?
  2. Would more RAM help?

Or in the end, is it just the size of my website (400+ pages)?

image
image1310×376 74.9 KB

2

It’s a rather large website, and we’re constantly working on refining and improving performance with large websites. I don’t think this will ever end, everybody’s website is always growing, though not always in the same dimension. Pages, text, images, large assets all make the website large but strain the software or the system in different ways.

Certainly a modern Mac is very different, and an Apple Silicon processor is much faster than Intel chips, even more than the age would suggest. Also important is the associated disk, which while technically perhaps still an SSD, has seen major performance improvements.

We’re working on keeping the RAM needs reasonable, so while in the currently released version there are instances where RAM usage will balloon, that’s a bug and we have already significantly improved it for the next update, and expect to be keeping it in check.

So part of the answer is yes a faster Mac will help. The other part is we’re working on improving Sitely all the time.

What can help us is:

  • if Sitely beachballs, you can use the system Activity Monitor application to record a sample, and send it to us
  • if Sitely consistently is using a lot of memory or CPU, duplicating the project and cutting it down to the minimal project that still causes the issue, and sending that to us, will also help in troubleshooting and debugging

Thanks.

1 Like
3

Thank you Duncan. I hadn’t realized speed of SSD matters. I’ll let you know if I can narrow things down to a culprit page.