bret at pectopah
Jan 30, 2012, 6:39 AM
Views: 1466
Permalink
|
Hi Zdravko,
If your templates call publish_another() in every story, that's probably
causing a good portion of the slowness you're experiencing.
What happens if you temporarily disable that?
All the best,
Bret
On Mon, 2012-01-30 at 08:15 +0100, Zdravko Balorda wrote:
> Hi, Matthew!
> I remeber, yes. here, I am chasing speed of a whole republish. When you
> have 25000 stories, and if it takes 2-3seconds on a story it takes a while. :)
> But not much can be done, except perhaps in templates. I use publish another
> in every story, unfortunately. Fanny thing though, perl takes 70% of CPU time.
> What is it doing? :)
> Zdravko
>
> Matthew Rolf wrote:
> > I started a thread on this topic a while ago relating specifically to the API:
> >
> > http://www.gossamer-threads.com/lists/bricolage/users/38869
> >
> > -Matt
> >
> > On Jan 26, 2012, at 12:03 PM, David E. Wheeler wrote:
> >
> >> On Jan 26, 2012, at 6:40 AM, Zdravko Balorda wrote:
> >>
> >>> I'm trying to otpimize publishing for speed, now. Using
> >>> bric_queued leaves apache for UI, which is good. There are
> >>> left two main processes working on publish: perl (bric_queued) and
> >>> postgres. Interestingly, the two grabs all 100% of one CPU, while
> >>> leaving the other lose. There are two in my box.
> >>> System time is very low: 3.3%.
> >>> Seems quite optimal. Are there any better practices?
> >> Not really. The best way to minimize publish time is to keep your templates simple, and don’t over-call pubish_another().
> >>
> >> Best,
> >>
> >> David
> >>
> >
> >
>
>
--
Bret Dawson
Producer
Pectopah Productions Inc.
(416) 895-7635
bret [at] pectopah
www.pectopah.com
|
