lisota, this is not related to the query. We do a very CPU-intensive transformation of the markup of each article in 2-pass (first parsing it to a DOM tree and then iterating node by node applying several transformation rules to create an in-memory representation).
There is definitely room for improvement, and we aim to drop the time substantially, but I’d recommend not using the RSS: it was kept in the plugin mostly to ensure backwards compatibility.
You can, instead, connect to your page using the Settings page and then your posts will be pushed to Instant Articles automatically on save, using our API, and one-by-one.
Does that help?
Thread Starter
lisota
(@lisota)
That does help. This is actually quite confusing. Between the plugin admin screens and the FB admin pages that have a spot for the RSS feed, I assumed that the plugin required some hybrid of RSS feed and API, but it isn’t clear when each of them get used.
In fact, it wasn’t clear to me at all that there was auto-publishing going on via the API until I looked at the article list in the Pages app, which is wildly different than the article list that appears in the RSS feed. Custom post types aren’t appearing in the RSS, but are appearing in Pages.
@lisota, I’ve taken note of your feedback — it’s much appreciated!
Also, regarding the performance, the latest release (v2.9 as of now), contains some significant improvements to performance. Could you give that a try and see if your experience is better?
I’m marking this as “resolved” for now.
