Hi Dimal!
I remember you were looking at your DEBUG logs a few months ago, and reported that you saw “ABSPATH” in your paths. Did you figure out where that came from, and if fixing your ABSPATH in wp-config would fix that issue?
Unfortunately, without a better understanding of how/where your preload is failing, we aren’t sure what problem to fix. We test Super Cache on sites with many posts, and aren’t seeing it stop after 20.
We’ve been iterating on the preload stuff a bit; making it work more reliably on hosts with tight limits. We’ll be releasing it in 1.10 soon once we work out a bug to do with gzip compression. But I see you’re already running 1.10-alpha now.
Where did you get it from? We don’t typically release an alpha build; that’s the version we use for the absolute latest in our repository. If you’re keeping up-to-date with our absolute latest from our repository, then installing 1.10 once it’s released won’t fix your preloading.
If you’d like us to check out what is going on with your preload, would you mind sending us your DEBUG log?
You’re welcome to post it here, but if you would like to send it to us privately, you can use the following contact form:
https://jetpack.com/contact-support/?rel=support&hpi=1
If you do, please include a link to this forum thread for context.