Hey @tremlas,
we increased the default batch size from 50 to 100 (for all tasks), which might be the reason for that.
You can modify that by using the filter shown here: https://docs.simplystatic.com/article/135-simplystatictasknamebatchsize
Hi @patrickposner, I tried with that filter which does seem to improve the update interval. However the activity log updates are still strange. My generation is currently about 10-11 minutes in length. The reported progress starts at “0 of 43” and then, after a minute or so updates to “43 of 228” where it remains for another six minutes. It then updates to “228 of 2457” but repidly reverts to “43 of 228”. For the next few minutes it will change to “228 of 2457” but again rapidly revert to “43 of 228”. In the last minute (or so) of the generation it then changes to “3400 of 3920” and reverts “228 of 2457”. Finally in the tail end of the generation it updates how I expect until the very end. My final status says “4013 of 4015” as shown below
[2025-03-07 15:39:53] Setting up
[2025-03-07 15:39:57] Fetched 4013 of 4015 pages/files
[2025-03-07 15:50:43] ZIP archive created: [link redacted]
[2025-03-07 15:50:43] Wrapping up
[2025-03-07 15:50:43] Done! Finished in 00:10:50
It looks like the update of the status is being updated by multiple threads???
(@patrickposner, As an aside, I also noticed that three of the generated files in the zip appear to have random chunks of the file omitted – meaning that the version in the generated zip file doesn’t match the previously generated version of the same file when I use version control to check the changes even though the source file has no changes – my testing for this shows it affects files at random but typically files towards the end of the file discovery process – I’ve never seen this with version 3.2.5.3 and again I wonder if there’s a multiple thread/process interaction that’s been added or adjusted….)
@tremlas I wonder if that is related to the object cache purge we implemented here: https://github.com/Simply-Static/simply-static/blob/65958a69a432d261610dd8f61de99494f7401c7e/src/class-ss-plugin.php#L210
We now clear the object cache before running the static export to avoid cached results from our DB table.
While not needed on solid web servers, the increasing adoption of (sadly messy) Litespeed server setups forced us to get that into the plugin to fight the constant “cache-all-the-things” behaviour LS servers do to sell better performance.
