My earlier suggestion of sending us the files still stands. I’d be happy to look at it. But without specifics I’m afraid we’re probably just guessing at causes and that’s not very productive.
From above:
sending me a direct message – you can zip up your file and and your stacks folder and drop them right in the slack window and it will send over the files even if they’re hundreds of megabytes.
I too am seeing beachballs either upon saving (I have disabled home page previews) or, more often, on quitting RW. I am using the latest RW6 and the latest Stacks plugin. Cannot say for sure that it is Stacks related, but the vast majority of my site pages use Stacks 3.
It is worrying… all the more so given that Realmac are full steam ahead on RW7 (according to their podcast). Hold fire chaps, get RW6 bulletproof first.
As you will see from my recent posts I was suffering from the spinning beachball. My grateful thanks to Isaiah who took a personal interest in my plight. He diagnosed that my site was far too large and complex. Its size was 228mb with a very large number of stacks. He advised me to split the site which I have done today. The largest portion of the site is now 155mb and I am pleased to say that the spinning beachballs have completely gone.
Richard is building quite a site. The size in MB belies the complexity. It’s really something to behold. I ran one of my internal analysis tools. I won’t go into details but I will say that it has more stank nodes in a single project file than I’ve ever seen before.
It has given me a great test case to test extremely complex documents – but in this case I think it’s safe to say that the file complexity is the source of the issue rather than a bug.
My recommendation to Richard was to cut the file into pieces (which apparently I had already recommended him do a while back – and this project is merely a piece of the total – wow!!!)
The other option is to potentially look into a CMS solution where the complexities of the layout can be defined once and the pages can be generated dynamically by the server using php – instead of designing hundreds of pages by hand.
@MortalWombatUK (or anyone else experiencing beachballs) – as Richard’s case very dramatically demonstrated… there is no single source for slow behavior, it can come in many forms, and is often due to a unique/outlier use case that developers may not know about.
Help us help you: send us your documents and/or stacks so that we can see the problem too and either help you work around it and fix any bugs that we find
Isaiah
Upgrading to El Capitan has solved a myriad of spinning beach-ball problems for me leaving only it’s brief appearance when saving the large file.
I’d suggest I won’t be the only one and I whole-heartedly recommend an upgrade to 10.11 to anyone ‘suffering’ to find out.
Upgraded to El Cap yesterday, and so far no spinning beachballs apart from saving files and previewing.