I think it would increase load times as well having to pull your data from a remote host instead of the local server.

We had to make quite a few adjustments, an advancement to the post cache and a specialized attachment cache -- just to name a few. We were forced to this method due to large attachment processing and manipulating. The average vBulletin owner has really no need for this kind of complexity, maybe a large specialty photo site. I spoke out because I thought @Zachery needed some support on his view/statements. This question seems to pop-up now and then, and I figured I could add some insight.

I wasn't questioning you or anything. I was just adding in response to the op. I'm sure you had reasons and it sounds like you made it work well.

No worries, I took your response as the good-natured intent that you meant. I am sorry if my response in anyway indicated that I did not. I try to write my responses for anyone reading the thread, the idea was to add additional helpful content that I decided to append to the end of the post. Sorry, I think I confused you in my effort to write to the general audience.

After reading it over, I should have started my reply with "I agree with you". I was really trying to explain why I needed such a monster and that for most people it is total overkill. I did not even get into the fact that we run a modified version of PHP where we run our caches in a common static memory module, so they do not have to be refreshed or rebuilt every page. All of this was done just to get back some of the performance loss you were indicating.

Your input is always welcome. :)

It's all good friend! Not like I was mad or anything. :) All good points and good discussion.:up: