Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Bricolage: users
Re: optimizing publishing
 

Index | Next | Previous | View Flat


david at justatheory

Feb 28, 2012, 11:36 AM


Views: 1394
Permalink
Re: optimizing publishing [In reply to]

On Feb 28, 2012, at 4:59 AM, Zdravko Balorda wrote:

> there appear to be one more issue regarding parallel publishing:
> publish_another() builds its own story queue, in memory. This requires
> some form of IPC between daemons or via database.
> I went for database approach:
> publish_another now creates a new job for a document if such a job
> doesn't exist already. Otherwise it merely pushes further its schedule
> time to current time. Story will then be published last. No need for
> flush_another_queue() anymore.

Well, it should go out as quickly as possible. IIRC the reason for the in-memory queue was so that it would iterate over the jobs and publish them immediately. But maybe not?

At any rate, your proposal seems quite sane to me.

> Also, publish_another inherits job priority from a calling job, instead
> setting it to document priority.

Yeah, it should probably be supported as a parameter, but should still default to the priority of the current job (or the highest priority job that calls publish_another() to schedule it).

> And, Bulk publish via UI should also schedule jobs under lowest priority.

Why lowest priority?

Thanks,

David

Subject User Time
optimizing publishing zdravko.balorda at siix Jan 26, 2012, 6:40 AM
    Re: optimizing publishing david at justatheory Jan 26, 2012, 9:03 AM
    Re: optimizing publishing david at justatheory Jan 26, 2012, 9:03 AM
    Re: optimizing publishing rolfm at denison Jan 27, 2012, 3:16 PM
        Re: optimizing publishing zdravko.balorda at siix Jan 29, 2012, 11:15 PM
            Re: optimizing publishing bret at pectopah Jan 30, 2012, 6:39 AM
                Re: optimizing publishing zdravko.balorda at siix Jan 31, 2012, 11:44 PM
                    Re: optimizing publishing zdravko.balorda at siix Feb 14, 2012, 12:03 AM
                        Re: optimizing publishing jaroskim at who Feb 14, 2012, 12:12 AM
                            Re: optimizing publishing zdravko.balorda at siix Feb 14, 2012, 12:39 AM
                                Re: optimizing publishing david at kineticode Feb 14, 2012, 11:23 PM
                                Re: optimizing publishing jaroskim at who Feb 15, 2012, 12:48 AM
    Re: optimizing publishing zdravko.balorda at siix Feb 15, 2012, 12:42 AM
    Re: optimizing publishing michael.fletcher at cbs Feb 15, 2012, 7:20 AM
    Re: optimizing publishing zdravko.balorda at siix Feb 16, 2012, 2:38 AM
        RE: optimizing publishing michael.fletcher at cbs Feb 16, 2012, 6:43 AM
    Re: optimizing publishing zdravko.balorda at siix Feb 17, 2012, 5:04 AM
    Re: optimizing publishing zdravko.balorda at siix Feb 21, 2012, 5:52 AM
        Re: optimizing publishing david at justatheory Feb 21, 2012, 11:01 AM
    Re: optimizing publishing zdravko.balorda at siix Feb 21, 2012, 10:30 PM
        Re: optimizing publishing david at justatheory Feb 22, 2012, 9:03 AM
    Re: optimizing publishing zdravko.balorda at siix Feb 23, 2012, 10:07 PM
    Re: optimizing publishing zdravko.balorda at siix Feb 28, 2012, 4:59 AM
        Re: optimizing publishing david at justatheory Feb 28, 2012, 11:36 AM
    Re: optimizing publishing zdravko.balorda at siix Feb 29, 2012, 1:09 AM
        Re: optimizing publishing leggn at denison Feb 29, 2012, 4:55 AM
        Re: optimizing publishing david at justatheory Feb 29, 2012, 10:50 AM
    Re: optimizing publishing zdravko.balorda at siix Mar 1, 2012, 1:22 AM
        Re: optimizing publishing david at justatheory Mar 1, 2012, 10:26 AM
    Re: optimizing publishing zdravko.balorda at siix Mar 1, 2012, 10:21 PM
        Re: optimizing publishing david at justatheory Mar 2, 2012, 9:11 AM

  Index | Next | Previous | View Flat
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.