I was hoping someone knew exactly how server intensive this hack is? I have a fairly large community (20-40 members on at a time) and since i have installed this wonderful hack my host is now barking at me for using too much CPU, MEM, SQL%. I'm on a shared host environment so I can not hog all the resources obviously, but this has not been a problem until I installed this hack, I believe.
CMX - do you know any ways to optimize the eShop/eBux system so it is less server intensive? I didn't know if there were any options I could take out of the internal code or simply disable the options that are the major server eaters, if you know what they are.
I LOVE this hack and my members have been loving it... I haven't had any technical issues... it is just the server usage is a problem. I was hoping you could share a few pointers. I also know that w/ every release it is more optimized and uses less queries, so I'll continue to upgrade (which seems to be every day with your pace! your awesome). Any help would be nice, thanks!
|