Andrew,
The problem with disabling caching is that your requests would always call the API – on EVERY page load. If that were to happen and you had a lot of visitors, you would be throttled or temporarily blocked by Amazon for making too many request per hour or per second.
You CAN disable the ‘cache-ahead’ process which may help. This feature reads all of the ASINs on a page (even a list page) and groups them together and does grouped calls to Amazon and caches the groups (which them makes it easier for the plugin to call the cached file because it looks for the ASIN in any previously grouped cache file). This feature is available in version 3.6.3 up – so if you do not have that version installed, update first and see if that helps you out more with the cache issues.
The cache-ahead option is located in the options under the advanced tab.
Let me know if you have any issues.
Warm regards,
Don
Sorry Don, I should be more clear.
I absolutely agree that caching is a must. My issue is with the large number of products on my site, caching using the db is creating a performance bottleneck well before I’m being throttled by Amazon.
By “performance bottleneck” I mean page load times of up to 15sec.
Having an option to disable the plugins native db caching option frees us up to use our own caching solution, static html files via cdn as an example. Which scales a lot better than the db does.
Hope that makes sense.
Thanks, Andrew
