CG-Amazon ready for primetime!

excellent!
i also had to change it in the call in index.php
now it’s time to make it look better with my css
thanks!

Glad you’re liking it. Let me know if you need any help, or find anything missing you’d like to see.
-d

I am finding it taking a remarkable amount of time to load…
Since i’ve added this plugin it’s taking between 5-10 seconds to load my page… Prior it was taking 1-2 seconds…
Is this normal?
Any ideas on pulling this back?
I am just pulling 3 items from my wishlists with graphics…

Yes, you need to make sure that cg-plugins/cache_amazon/ is writeable, and possibly all the directories up to the root of WP. Otherwise, CG-Amazon can’t write to cg-plugins, and you do LIVE lookups to amazon every pageload.
start with the cache directory, and test the page, and see if you get something written to cache_amazon. If you do, you’re done; if you don’t, continue up the directory path making folders accessible until you get something written into the cache folder.
-d

that didnt do anything and nothing has been written in those directories even after chmoding 777….
also i get these errors from time to time that go for pages down my site:
Warning: fread(): supplied argument is not a valid stream resource in /home2/olympus/public_html/xxxxx/cg-plugins/XMLParser.php on line 68

hmmm… okay, one at a time.
if things aren’t being written, that’s definitely the performance issue. did you chmod wp-content/, plugins/, and cg-plugins/ as well as cache_amazon/ ? I’m not sure whether php enforces it on a single folder, or actually on the entire hierarchy.
for the errors, I’m not sure why you are seeing them (they should all be redirected to an error handler, and I think all the error output is disabled). if you see an fread error, which shouldn’t come up as the open of the stream should have failed out, it means that stream was inaccessible for some reason (amazon is down or saturated, etc.).
-d

ok, everything is 777 now, at least the directories you said… now it’s better, but it’s now just consistantly at 5sec for page generation which seems high to me…
i do have /cg-plugins off the root directory as /cache_amazon is under /cg-plugins
is this correct, or should the cg-plugins be in the /wp-content/plugins dir?
thanks,
mat

It is not caching, I would try placing cg-plugins, et al, in the plugins directory and test from there.

i got it down to 2.956 seconds.
but that is still double what it should be….
i’ll try that replacing now

it’s still around 2.5 seconds
turning off the debugging helped significantly… but moving to other directories just created more problems

yet, still no files in the cache dir.

piginzen:
Grab the CG-PowerPack. Read the top-level readme, and in the cg-amazon extra stuff folder is the cg-amazon specific readme (with updates). Install that… the updated docs there should now be pretty clear as to what goes where, but post if you have questions.
THEN make sure in that new structuring that all the paths are writeable, and see if the cache files show up properly at that point.
I’m just getting confused as I haven’t had time to update the now-weeks-old CG-Amazon individual release, where the CG-PP version has numerous changes/fixes — and Beel and I both have gone through the install issues at this point and it certainly should ‘just work’ now.
ALSO, for my own sanity, try turning off the call to amazon (not the plugin, just the call), refresh a few times, see what your average pageload time is like. I do know that the times you are quoting sound like cg-amazon not being able to cache, but I thought I added debug code for it to complain loudly if it tried creating a cachefile and couldn’t…
In the worst case, I can do with you what I did with Beel, which is get an admin-level account on your system and poke around directly. For all I know, it’s something particular about your hosting config/versions that I haven’t hit myself yet (my own site dies on the new server I’m supposed to be moving to…).
-d

3 load times with out the amazon wishlist are:
41 queries.
1.334 seconds.
41 queries.
1.342 seconds.
41 queries.
1.358 seconds.

Okay, good to know. 41 queries is a lot, but you’re getting decent computed times.
Let me know if the PowerPack installation readmes don’t make a lot more sense out of all of this… ??
-d

Yeah, i had thought 41 queries is a lot too… I do have a lot of plugins… these are the ones i am using:
Blogtimes, Condensed Content for Date and Category Archives, On this Day, Related Posts, WP Statistics, StatTraq, Subscribe to Comments, TimeSince, Usersonline, WeatherReport, & WP Free-Stats. In addition, my friend wrote a hack to increment page view displays for individual entries.
Does this sound normal for all these plugins?