Comments on: Speed up the publish time of your store http://www.ystoreblog.com/blog/2007/10/speed-up-the-publish-time-of-your-store/ Tips, Tricks, and Best Practices Mon, 23 Jan 2012 15:16:27 -0800 http://wordpress.org/?v=2.9.2 hourly 1 By: Albert http://www.ystoreblog.com/blog/2007/10/speed-up-the-publish-time-of-your-store/comment-page-1/#comment-102396 Albert Sat, 28 Jun 2008 04:27:38 +0000 http://ystoreblog.com/blog/2007/10/speed-up-the-publish-time-of-your-store/#comment-102396 Just an observation of my own, I have two stores with about 800 pruduct pages each. Each product has from 5 to 15 colors. I have seperate image for each color so the customer can view it in the color of choice. With all my product images loaded in a subdirectory in the web hosting side. publishing takes less than 3 min. with all the images loaded in the "Files" directory on store manager side, publishing takes over half an hour. I would recommend keeping your "Files" directory in store editor as small as possible and utilize the web hosting side as much as possible. That should reduce your publishing time since it does not republish whats in the webhosting side. Just an observation of my own,
I have two stores with about 800 pruduct pages each. Each product has from 5 to 15 colors. I have seperate image for each color so the customer can view it in the color of choice.

With all my product images loaded in a subdirectory in the web hosting side. publishing takes less than 3 min.

with all the images loaded in the “Files” directory on store manager side, publishing takes over half an hour.

I would recommend keeping your “Files” directory in store editor as small as possible and utilize the web hosting side as much as possible.

That should reduce your publishing time since it does not republish whats in the webhosting side.

]]> By: Jacob Swartwood http://www.ystoreblog.com/blog/2007/10/speed-up-the-publish-time-of-your-store/comment-page-1/#comment-102395 Jacob Swartwood Fri, 26 Oct 2007 16:56:42 +0000 http://ystoreblog.com/blog/2007/10/speed-up-the-publish-time-of-your-store/#comment-102395 Grr... scratch that. Using ONCE :page inside a FOR-EACH-OBJECT definitely doesn't work the way I thought. I'll pollute this thread again if I figure anything else out. Grr… scratch that. Using ONCE :page inside a FOR-EACH-OBJECT definitely doesn’t work the way I thought. I’ll pollute this thread again if I figure anything else out.

]]> By: Jacob Swartwood http://www.ystoreblog.com/blog/2007/10/speed-up-the-publish-time-of-your-store/comment-page-1/#comment-102394 Jacob Swartwood Thu, 25 Oct 2007 22:13:18 +0000 http://ystoreblog.com/blog/2007/10/speed-up-the-publish-time-of-your-store/#comment-102394 Sorry, that example code didn't tab appropriately. Pretend each line is indented relative to the previous line. Sorry, that example code didn’t tab appropriately. Pretend each line is indented relative to the previous line.

]]> By: Jacob Swartwood http://www.ystoreblog.com/blog/2007/10/speed-up-the-publish-time-of-your-store/comment-page-1/#comment-102393 Jacob Swartwood Thu, 25 Oct 2007 22:11:00 +0000 http://ystoreblog.com/blog/2007/10/speed-up-the-publish-time-of-your-store/#comment-102393 Ivan, ONCE :page is great too (if not better than ONCE :publish.) It may actually save you from your editor being slow in addition to faster publish times. Rather than use a "trick" to do your nav once per publish, you could theoretically do it once (actually just once.) Also, with this method, you shouldn't even need to check whether or not you are in the editor to hide your nav. Try this and see what you think... <code> WITH-OBJECT :index ONCE :page ... </code> I'm not positive, but it would seem that with the object "index" it is only generating the code that would follow once. Since there is only one page "index" in the store, it will only generate that nav once. On the same note... it would seem that you could use ONCE :page inside a FOR-EACH-OBJECT loop so that you wouldn't have to run any code in the body of the loop for any object twice (if that makes sense.) Since I have not contact with anyone at Yahoo!, I have no idea how this actually works or if it is doing exactly what I think it is. It does appear to work though. - Jacob Swartwood Ivan,
ONCE :page is great too (if not better than ONCE :publish.) It may actually save you from your editor being slow in addition to faster publish times. Rather than use a “trick” to do your nav once per publish, you could theoretically do it once (actually just once.) Also, with this method, you shouldn’t even need to check whether or not you are in the editor to hide your nav. Try this and see what you think…


WITH-OBJECT :index
ONCE :page
...

I’m not positive, but it would seem that with the object “index” it is only generating the code that would follow once. Since there is only one page “index” in the store, it will only generate that nav once. On the same note… it would seem that you could use ONCE :page inside a FOR-EACH-OBJECT loop so that you wouldn’t have to run any code in the body of the loop for any object twice (if that makes sense.)

Since I have not contact with anyone at Yahoo!, I have no idea how this actually works or if it is doing exactly what I think it is. It does appear to work though.
- Jacob Swartwood

]]>